Conversation
When we hit an unexpected server response, summarize it with the status code, status message and the response body instead of dumping the raw Haskell data-structures.
|
No worries about Haskell, but could you copy/paste or screenshot the new output for the review? (preferably before/after) or is it untested / hard to trigger? |
We can also stash the longer message in ucm and mention a debug command to display it. |
|
My inclination would be to have add an Only downside would be if something isn't reproducible the message is lost, but if it's from a web-request I can always look up the logs to see what happened anyways 🤷🏼♂️ |
|
An idea that came up in our standup was to display the request id and have the user report that, and then make @ChrisPenner look up ids on the server each time. 🙃 |
When we hit an unexpected server response, summarize it with the status code, status message and the response body instead of dumping the raw Haskell data-structures.
This fixes #5341 though I think we should probably log the actual request and response to a file somewhere.
Excuse my poor haskell here—this is more of a draft than anything, as I'm not sure what the appropriate style is.