Spinning up a devnet via tenderly devnet spawn-rpc ... results in all output being piped to stderr. This makes error handing tricky when being used in the context of scripts because rpc url and errors end up getting piped to the same destination.
We're currently redirecting stderr to stdout so we can capture the rpc data in a file, but errors end up in that file if there is an error:
The rpc url data should be output to stdout and errors should go to stderr so our scripts are able to easily handle errors. This was we could simply pipe the data to our file and see errors in the console directly.
Workaournd
We are able to see errors in the file that is outputted, so theoretically we could write another script to first check the file for an error and output this to the console.
Description
Spinning up a devnet via
tenderly devnet spawn-rpc ...results in all output being piped to stderr. This makes error handing tricky when being used in the context of scripts because rpc url and errors end up getting piped to the same destination.We're currently redirecting stderr to stdout so we can capture the rpc data in a file, but errors end up in that file if there is an error:
tenderly devnet spawn-rpc --template \"e2e-latest\" --project \"project\" --output json 2> ./tenderly/.tenderly.jsonExpected behavior
The rpc url data should be output to stdout and errors should go to stderr so our scripts are able to easily handle errors. This was we could simply pipe the data to our file and see errors in the console directly.
Workaournd
We are able to see errors in the file that is outputted, so theoretically we could write another script to first check the file for an error and output this to the console.