DUNE-DAQ / DUNE-DAQ/runconftools
[Feature]: No operation repo case
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 3
Description
Description
There are some usages of the Runconftools that only require the base repository, e.g. using emulation data. We should introduce a mode in which we don't need to pass operation url in case it's not necessary.
Potential impact radius
Small/Isolated
Reason for change
Code in runconf_ui might be simplified. Also some operations.
Suggested implementations
No response
Testing suggestions
No response
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 tracing how runconftools and runconf_ui currently require the operation URL, including the emulation-data use case. The work is done when base-repository operations can run without an operation URL while existing operation-based behavior remains supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100