signalling a system doesn't set an error code on an error
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 50/100
Research direction
Start at the mq.sh sem -signal command handling and compare its error paths with the sem -wait behavior shown in the issue. Verify that failed signalling returns a nonzero status while successful signalling remains successful; reproduce the examples with echo $? to confirm the result.
Written by the indexing model from the issue text.
Description
Compare e.g.:
$ mq.sh sem -wait odroidc4_1
Attempting to grab lock you already own with the same key. Please explicitly release
Failed to acquire lock for system (odroidc4_1)
$ echo $?
2
With
$ mq.sh sem -signal odroidc4_1
Attempting to unlock system odroidc4_1 that you do not hold
$ echo $?
0
Or
$ mq.sh sem -signal odroidc4_1
Attempting to unlock system odroidc4_1 with the wrong key!
$ echo $?
0
- Dominant language
- Shell
- Stars
- 4
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
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.
Similar issues
-
good-start
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
VilnaCRM-Org/user-service#497 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conda-forge/spacy-feedstock#177 ·
-
area:jail bug security severity:low track:open-source
Difficulty 1/5 Under an hour Newbie friendliness 75/100