Hub Thread Safety
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by locating Hub's public interface and the register-handler, remove-handler, and lockout functions named in the issue. Inspect how they interact with the service's main thread; done means each public operation is safe when used in parallel with that thread, though the issue names no tests or validation command.
Written by the indexing model from the issue text.
Description
Transferred from project8
Public interface functions for services like hub should be thread safe, as they raise the possibility that they'll be used in parallel with the service's main thread.
Hub provides a public interface to the register- and remove-handler functions. These should be made thread safe.
Hub provides a public interface to the lockout functions that should be made thread-safe.
- Dominant language
- C++
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No 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 driplineorg/dripline-cpp
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
driplineorg/dripline-cpp#131 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
driplineorg/dripline-cpp#121 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
driplineorg/dripline-cpp#114 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
driplineorg/dripline-cpp#103 ·
-
Reactivate OP_RUNOpen
Difficulty 5/5 Over a week Newbie friendliness 35/100
driplineorg/dripline-cpp#102 ·
All issues in driplineorg/dripline-cpp
Similar issues
-
Status: Needs confirmation Status: Needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
A-combat P-low S-ready-to-start task
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
bug intrinsic medium priority rt_lib
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day