manage.sh update can leave every service stopped
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 66/100
Research direction
Start in the update branch of manage.sh, where services are stopped before git reset --keep @{upstream} runs, and check what happens when the reset fails. Pick either a check that runs before any service is stopped or a restart on the failure path, then update the steps in docs/operating/upgrading.md to match. Done when a refused reset leaves the services running, or restarts them, and the upgrade docs describe that behaviour.
Written by the indexing model from the issue text.
Description
manage.sh update stops the services before running git reset --keep @{upstream}. When the reset refuses because tracked files have local edits, the script exits and the services stay stopped.
We could run the reset (or a dry check) before stopping anything, or restart the services when the update fails. docs/operating/upgrading.md would then need updating.
- Dominant language
- Python
- Stars
- 16
- Forks
- 5
- Avg merge
- 8h 23m
- Merged PRs (30d)
- 18
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from smswithoutborders/RelaySMS-Publisher
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
smswithoutborders/RelaySMS-Publisher#230 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
smswithoutborders/RelaySMS-Publisher#227 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
smswithoutborders/RelaySMS-Publisher#226 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
smswithoutborders/RelaySMS-Publisher#222 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
smswithoutborders/RelaySMS-Publisher#221 ·
Maintainers usually reply within 1 day
All issues in smswithoutborders/RelaySMS-Publisher
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
521xueweihan/HelloGitHub#4237 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
jejjohnson/gaussx#721 ·
Maintainers usually reply within 1 day
-
mock-core-configs/etc/mock/rocky-10-riscv64.cfg contains the wrong architecture in config_opts['root']Possibly taken @jasonmontleon claimed this 4 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 94/100
rpm-software-management/mock#1834 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
elastic/elastic-otel-python#683 ·
Maintainers usually reply within 1 day
-
ci-rerun: collect.py fails a whole pr-babysit cycle on one transient GitHub 5xx and never retriesOpenfollow-up
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day