rust-lang / rust-lang/rust-playground
Better handling of server errors
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 267
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 6
Description
I once got a 502 Bad Gateway and this is what was shown:
Response was not JSON: SyntaxError: Unexpected token < in JSON at position 0
A different message would be nicer, e.g. that the server couldn't be reached.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named in the report. Start by reproducing a 502 response in the Rust Playground and locate the entry point that parses and displays the response; done means server errors show a useful reachability message instead of a JSON parsing error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100