RequestsJSONDecodeError returned when nylas has a 502
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 109
- Forks
- 85
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 1
Description
Describe the bug
When nylas has an internal server error, a RequestsJSONDecodeError is returned
To Reproduce
Run any API until nylas returns a 502...? The code for this specifically was running messages.list
// Helps us with reproducing the error :)
Expected behavior
Returns a NylasApiError instead of RequestsJSONDecodeError
SDK Version:
6.4.0
Additional context
Contributor guide
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
Start by reproducing the 502 response through messages.list, then trace the SDK's response and exception handling to find where RequestsJSONDecodeError escapes. Check whether the existing tests cover non-JSON server errors. Done means a 502 produces NylasApiError instead, with regression coverage for that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100