awslabs / awslabs/shuttle

Missing vector clock update for Unfair BatchSemaphore release

Open Beginner friendly
#298 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
1.1k
Forks
59
Avg merge
4d 2h
Merged PRs (30d)
15

Description

No clock update here: https://github.com/awslabs/shuttle/blob/c8a46d3965048df3207ec920dae066bc9c4d9d89/shuttle-core/src/future/batch_semaphore.rs#L608-L612, but clock update here: https://github.com/awslabs/shuttle/blob/c8a46d3965048df3207ec920dae066bc9c4d9d89/shuttle-core/src/future/batch_semaphore.rs#L268-L274

Contributor guide

Open the contributing guide

Research direction

Start in shuttle-core/src/future/batch_semaphore.rs, comparing the release code around lines 608-612 with the clock update around lines 268-274. Trace the Unfair BatchSemaphore release path and verify that its vector-clock behavior matches the referenced path; the relevant concurrency tests should pass when the issue is fixed.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
testing
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
78/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.