DUNE-DAQ / DUNE-DAQ/runconftools
[Bug]: No clear exception thrown when remote repository is not available
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 3
Description
Description
During a gitlab outage, software depending on runconftools (runconf-ui) was not able to identify that the remote repository was not available. We should make it obvious.
Steps to reproduce
Running runconf-ui in remote state with gitlab down. We should try to run with a fake repo to reproduce the error.
Version and environment
this was develop and also 5.6.2.
Impact
Small/Isolated
Anything else?
No response
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 runconf-ui in remote state with GitLab unavailable or a fake repository, then trace the exception path for the failed remote access. The issue is done when that outage produces an obvious, identifiable exception instead of leaving the application unable to indicate what happened.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100