ObArray copy constructor passes allocator unsafely
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 a version change for obproxy, please also provide the output of obproxy -V.
Mapping relationship for the "Target Branch" and "Iteration" properties on the right side:
- Is this a temporary version provided by RD?: No / xxx temporary provision
- Reproducibility: Always / Occasional / 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
No source file, test, reproduction, or version output is provided. Start by locating ObArray's copy constructor and its allocator-handling path, then inspect existing tests for this container. Done means the allocator is passed safely and a regression test covers the reported construction.
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