JuliaLang / JuliaLang/Distributed.jl
Move away from using sticky tasks to avoid races (`@async` -> `@spawn`)
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 55
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/JuliaLang/Distributed.jl/pull/122 demonstrates tests pass robustly now when multithreading, but it requires keeping @async as using @spawn is known to introduce races like #124
https://github.com/JuliaLang/Distributed.jl/pull/122#discussion_r1929661983 is a good contender for a place to start trying to fix thread safety properly.
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.
Research direction
Start with PR #122, especially discussion_r1929661983, and read issue #124 for the race condition context. Determine the scope of fixing thread safety while replacing sticky-task usage; the issue does not identify files, tests, or a more specific completion criterion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100