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.

Sign up for GitHub

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

Jump to bottom

improve stack-traces from tahoe #679

Open

meejah opened this issue Oct 6, 2022 · 0 comments

Labels

Collaborator

meejah commented Oct 6, 2022

From @crwood: so there is way to have tahoe omit the HTML-ization of HTTP 500 error bodies (from the WAPI docs):

Unusual exceptions may result in a 500 Internal Server Error as a catch-all, with a default response body containing a Nevow-generated HTML-ized representation of the Python exception stack trace that caused the problem. CLI programs which want to copy the response body to stderr should provide an “Accept: text/plain” header to their requests to get a plain text stack trace instead.

We should ensure that magic-folder's tahoe-API usage includes the right header to get plain-text traces instead of HTML.

meejah added the enhancement label

crwood mentioned this issue

HTML-ized Tahoe-LAFS WAPI errors are unwieldy gridsync/gridsync#573

Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment