Bad error reporting for download failures
Open
good first issue
- Dominant language
- Python
- Stars
- 723
- Forks
- 178
- PR merge metrics
- No merged PRs in 30d
Description
If laika fails to download all orbits with "RuntimeError: No orbit data found on either servers" then there is no printout of what actually went wrong.
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the orbit-download code that raises the exact "No orbit data found on either servers" RuntimeError, then inspect how failures from both servers are handled. Done means the existing failure message also reports what went wrong during the download, with the relevant tests passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100