-
Notifications
You must be signed in to change notification settings - Fork 593
Open
Labels
T-feature-requestType: Adding a brand new feature (not to be confused with improving an existing feature).Type: Adding a brand new feature (not to be confused with improving an existing feature).from-communityThis originated from the community :)This originated from the community :)
Description
Problem Statement
Right now, if you run a nr test and it fails fails, you might get something like this:
[battleships] Testing test::integration::success::combat_wins::test_host_wins_by_sinking_all_ships ... FAIL
Failed calling external resolver. ErrorObject { code: ServerError(-32702), message: "Assertion failed: Failed to get a note", data: None }
The problem is that this log doesn't provide any context regarding what the issue is. It's very hard to debug the issue itself without being at least knowing what action in the contract (or test) generated the error
Proposed Solution
It would be great if the error would include a stacktrace that pointed to what action originated the error
Example Use Case
No response
Alternative Solutions
No response
Additional Context
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
T-feature-requestType: Adding a brand new feature (not to be confused with improving an existing feature).Type: Adding a brand new feature (not to be confused with improving an existing feature).from-communityThis originated from the community :)This originated from the community :)