Repository navigation
deps: threadteam 0.1.3 in the lock - #152
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves the lock from threadteam 0.1.2 to 0.1.3. Only the
threadteamentry changes; the caret requirement0.1.0stays.threadteam 0.1.3 (tensor4all/threadteam-rs#10) changes how team members wait. Reserved polling spins with PAUSE only, and when a scope is oversubscribed, join and barrier waits yield after a short spin. This fixes the stacked-thread slow mode reported in tensor4all/faer#107: on broccoli at 16T x20, 0/20 runs are slow, against 5/20 on 0.1.2. Participant pinning is opt-in and stays off by default; the leader is never pinned.
Verification:
cargo check --locked --workspace --all-targetspasses.🤖 Generated with Claude Code