Open-EO / Open-EO/openeo-python-client
Better handling of corrupt config/refresh token file
Open
Nobody has claimed this yet.
auth
configuration
feature request
good first issue
low hanging fruit
usability
- Dominant language
- Python
- Stars
- 217
- Forks
- 56
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
see https://discuss.eodc.eu/t/authentication-jsondecodeerror/190/3
existing but corrupt refresh token fails with JSONDecodeError and hard to examine stack trace
if json config file fails to load properly, there should be a better error message
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
Start by reproducing the JSONDecodeError with an existing corrupt refresh-token or JSON config file, then trace the config and refresh-token loading entry point. Done means malformed JSON produces a clearer, user-facing error message instead of only the hard-to-examine stack trace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100