We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The traces are super useful for debugging the frontend. But they also are quite verbose and hard to browse.
Debugging would be much easier if we had a tool to interactively browse traces.
A cheap way of doing that could be to parse the (tree) traces and reshape them as JSON, so that we can jless them.
jless
jless offers everything we want there: it's super fast, it can search efficiently into data, it's easy to fold the data, etc.
I suspect #686 is not so hard to fix. But currently, debugging is a huge pain because the logs are hard to browse.
The text was updated successfully, but these errors were encountered:
@W95Psp any updates on this or do you want to push it to next week?
Sorry, something went wrong.
@Nadrieril actually killed a whole bunch of issues in the frontend, so I don't think this issue is urgent any longer
Ok, closing then
No branches or pull requests
The traces are super useful for debugging the frontend.
But they also are quite verbose and hard to browse.
Debugging would be much easier if we had a tool to interactively browse traces.
A cheap way of doing that could be to parse the (tree) traces and reshape them as JSON, so that we can
jless
them.jless
offers everything we want there: it's super fast, it can search efficiently into data, it's easy to fold the data, etc.I suspect #686 is not so hard to fix. But currently, debugging is a huge pain because the logs are hard to browse.
The text was updated successfully, but these errors were encountered: