tv_nsec of timespec more than one second causes EINVAL in call to pthread_cond_timedwait
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- rust
- Domain
- operating-systems
Research direction
Start by locating the Rust implementation and call site for pthread_cond_timedwait, then inspect how timespec values reach that call. Reproduce the EINVAL case with tv_nsec greater than one second; done means valid timeout values no longer trigger this error.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- Rust
- Stars
- 66
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 elast0ny/raw_sync-rs
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
elast0ny/raw_sync-rs#34 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
elast0ny/raw_sync-rs#30 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
elast0ny/raw_sync-rs#28 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
elast0ny/raw_sync-rs#22 ·
-
Memory lossOpen
Difficulty 4/5 3-5 days Newbie friendliness 25/100
elast0ny/raw_sync-rs#20 ·
All issues in elast0ny/raw_sync-rs
Similar issues
-
documentation priority:p2 type:chore
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
dispatch:sol-high documentation
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
carrick-sh/carrick#768 · 1 comment ·
Maintainers usually reply within 1 day
-
correctness postgres tursopg
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
tursodatabase/turso#10442 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
ankitects/anki#5864 · 1 reaction ·
Maintainers usually reply within 2 days
-
area: config effort: S good first issue P3 type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
ferenyl/azuredevopstui#63 ·