Replies: 2 comments 10 replies
-
|
I wonder if it is possible to make some of the Honeycomb traces public. @Mirko-von-Leipzig - does Honeycomb have such a feature? If that's possible, we could make traces from the NTX builder available to select users. |
Beta Was this translation helpful? Give feedback.
-
|
Something that may also be a fairly quick win is to emit more verbose logs on execution errors for those that are testing against a local node. Currently, I believe if you want any details about your network transactions, you need to explicitly add a print somewhere in the node binary to output relevant information. If a flag or something similar existed to output more NTX logs (maybe even to a file or something), we can prompt users to try a local node first and see what the outcome is. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
After the recent challenges while debugging network accounts (AggLayer), I thought about ways of letting the users know what went wrong with processing their note. The creation of the note may be successful, but its processing might fail for various reasons (e.g. currently it could fail because the note script is previously unseen by the node and it can't fetch it by its root from
DataStore, though maybe we can address this particular scenario via this)Could we somehow make the error trace available to the sender? Maybe this could become accessible via gRPC (it's probably easier to make this accessible to anyone rather than just the sender)?
The main advantage would be that our node team wouldn't have to dig into node logs and debug every failed network tx for the user/dev. This is already painful today, and I'm assuming will become even more so once more devs are onboarded.
Beta Was this translation helpful? Give feedback.
All reactions