manage.sh logs --unit fails on a named instance
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
The bug is in the logs subcommand of manage.sh, which builds the systemd unit name relaysms-publisher-<name>.service without the instance name. Compare it with how other subcommands call the unit_name_for helper and switch logs --unit to the same pattern. Done when manage.sh logs --unit <name> finds the unit on an install made with --instance-name, and the change is verified by running that command on such an install.
Written by the indexing model from the issue text.
Description
manage.sh logs --unit <short name> builds relaysms-publisher-<name>.service without the instance name, so on an install made with --instance-name it finds no unit.
We could build the name with unit_name_for "relaysms-publisher-${name}.service", as the other commands do.
- Dominant language
- Python
- Stars
- 16
- Forks
- 9
- Avg merge
- 8h 41m
- Merged PRs (30d)
- 26
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
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
smswithoutborders/RelaySMS-Publisher#219 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
smswithoutborders/RelaySMS-Publisher#218 ·
Maintainers usually reply within 1 day
All issues in smswithoutborders/RelaySMS-Publisher
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
aws-samples/sample-per-model-bedrock#782 ·
Maintainers usually reply within 1 day
-
Google text documents are base64-encoded twicePossibly taken @feiiiiii5 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
coveragepy/coveragepy#2364 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100