Better Error Reporting for Failed HTTP Requests #93
Labels
No labels
accessibility
backport to lts
bug
code
critical
cygwin
documentation
duplicate
error reporting
external
feature
feedback
good first issue
help wanted
infrastructure
invalid
investigate
language spec
logs
lti
lts only
mac
maybe
qtype:bigbox
qtype:checkoff
qtype:expression
qtype:fileupload
qtype:multiexpression
qtype:multiplechoice
qtype:number
qtype:pythoncode
qtype:pythonic
qtype:pythonliteral
qtype:richtext
qtype:smallbox
question
question types
sandbox
security
syntax highlighting
ui/ux
wontfix
wsl
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
catsoop/catsoop#93
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
If something goes wrong with a submission on the JS side, we currently get a totally inscrutable error message that's always related to the JavaScript error that occurred, and which doesn't really help us figure out the actual underlying issue. We should try to do better.