Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Output FAULT messages to VSCode message pane? #108

Open
roschler opened this issue Jun 22, 2021 · 3 comments
Open

Output FAULT messages to VSCode message pane? #108

roschler opened this issue Jun 22, 2021 · 3 comments
Labels
question Further information is requested

Comments

@roschler
Copy link

Currently FAULT messages don't get output to the VSCode PROBLEMS, TERMINAL or other output areas. You have to go to the transaction detail screen in the DevTracker to see the fault message, which means you have to know which block to go to and also know in the first place that a FAULT occurred. Easy when you're still in the early stages of dev but progressively harder workflow later (my two cents). I would like to see those messages in the TERMINAL area and even better, have that window pop to the foreground automatically if a FAULT message was logged if that is possible.

@devhawk devhawk transferred this issue from N3developertoolkit/neo-blockchaintoolkit-library Jun 25, 2021
@djnicholson
Copy link
Contributor

If we do this, I think we'd first need a change to Neo Express to output FAULTs to the console (using some format that the DevTracker expects and parses). This behavior could probably be hidden behind a flag.

@djnicholson
Copy link
Contributor

Opened neo-project/neo-express#155 for the Neo Express suggestion.

@devhawk
Copy link
Contributor

devhawk commented Jan 18, 2023

As of June 2021, the ExpressLogPlugin writes transaction execution failures to stderr. DevTracker shows the full Express output in a terminal window. TX Faults are shown in red in order to distinguish them from other messages. @roschler is this sufficient?

Example:
image

@devhawk devhawk added the question Further information is requested label Jan 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants