Fix incorrect lock usage in object manager
Open
Nobody has claimed this yet.
dima
type: bug
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 339
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 52
Description
Environment
(Required) Please provide the output of bin/observer -V. If this test also involves changes to the obproxy version, please also provide the output of obproxy -V.
Mapping relationship for the "Target Branch" and "Iteration" attributes on the right side:
- Is this a temporary version provided by RD?: No / xxx temporary provision
- Reproducibility: Always / Intermittent / Uncertain / Other
Contributor 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.
Research direction
The issue names an object manager but provides no source file, test, reproduction steps, or version output. Start by locating the object manager and its lock usage, then identify a reproducible incorrect-lock scenario and the relevant existing tests. Done means the locking behavior is corrected and the regression is covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100