after dynamic_flow test, all configs left installed.
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
won't see this on github, but working on personal server,
every time I run the dynamic_flow, the cleanup output looks fine,
but when I check afterward, all the configurations are still there.
work-around:
sr3 cleanup # response tells you the value of DangerWillRobinson, say it's 27
sr3 --dangerWillRobinson=27 remove
It only affects local testing... but confuses me from time to time (falsifying any subsequent test.)
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 locating the dynamic_flow test and the cleanup handling behind the shown sr3 cleanup and sr3 --dangerWillRobinson=27 remove commands. Reproduce the test, then inspect why cleanup reports success while configurations remain installed. Done means the test leaves no configurations behind and subsequent tests are not affected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100