Debugger: render code snipet in CLI on error (#494)(#490) #494
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dg
reviewed
Jun 9, 2021
dg
reviewed
Jun 9, 2021
Member
|
I'm gonna try to tweak it a little more. |
dg
changed the title
dg
pushed a commit
that referenced
this pull request
Jun 15, 2021
Co-authored-by: Jan Barášek <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rel #490
A simple tool for plotting an uncaught exception (or other error) directly to the terminal in CLI mode. It makes it very easy to debug the application on the server.
Real example:
Thanks!