Debugging tip : How do I know which param is causi...
# general
c
Debugging tip : How do I know which param is causing the issue ?
Copy code
error: Program failed with an unhandled exception:
    error: Traceback (most recent call last):
      File "/usr/local/bin/pulumi-language-python-exec", line 85, in <module>
        loop.run_until_complete(coro)
      File "/usr/local/anaconda3/lib/python3.7/asyncio/base_events.py", line 573, in run_until_complete
        return future.result()
      File "/usr/local/anaconda3/lib/python3.7/site-packages/pulumi/runtime/stack.py", line 73, in run_in_stack
        raise RPC_MANAGER.unhandled_exception.with_traceback(RPC_MANAGER.exception_traceback)
      File "/usr/local/anaconda3/lib/python3.7/site-packages/pulumi/runtime/rpc_manager.py", line 67, in rpc_wrapper
        result = await rpc_function(*args, **kwargs)
      File "/usr/local/anaconda3/lib/python3.7/site-packages/pulumi/runtime/resource.py", line 325, in do_register
        resolver = await prepare_resource(res, ty, custom, props, opts)
      File "/usr/local/anaconda3/lib/python3.7/site-packages/pulumi/runtime/resource.py", line 88, in prepare_resource
        serialized_props = await rpc.serialize_properties(props, property_dependencies_resources, res.translate_input_property)
      File "/usr/local/anaconda3/lib/python3.7/site-packages/pulumi/runtime/rpc.py", line 68, in serialize_properties
        result = await serialize_property(v, deps, input_transformer)
      File "/usr/local/anaconda3/lib/python3.7/site-packages/pulumi/runtime/rpc.py", line 198, in serialize_property
        raise ValueError(f"unexpected input of type {type(value).__name__}")
    ValueError: unexpected input of type tuple
    error: an unhandled error occurred: Program exited with non-zero exit code: 1
w
Unfortunately I don’t this there is currently any good way to diagnose where this came from. The error message here should be updated to have more context. Also - I believe we are already tracking a suggestion to do this type checking earlier so that it can be reported synchronously with the real call stack. Since the error mentions a tuple - I suspect the issue is an errant comma somewhere.
👍 1