pcdshub / pcdshub/engineering_tools
Handle check_for_status gracefully in get_info.py
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 36
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 3
Description
RIght now, the call to r.raise_for_status() is not within a try/except block. Since it can throw exceptions, it should be in one so the exception can be handled properly with descriptive output.
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 in get_info.py and locate the call to r.raise_for_status(). Run the script or its existing checks to observe how the exception currently surfaces. Done means failures from that call are handled and produce descriptive output instead of escaping unhandled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100