Skip to content

The WeightSynchronizer FFI derived the host staging slot as shard_idx % num_shards, which only works if a slice's device ordinals are contiguous and aligned to a multiple of num_shards. Device ordinals are not guaranteed to be, so pass the staging slot explicitly as a range-checked logical_shard_idx input instead of deriving it from the device ordinal.#385

Open
copybara-service[bot] wants to merge 1 commit into
mainfrom
test_951205209

Conversation

@copybara-service

@copybara-service copybara-service Bot commented Jul 21, 2026

Copy link
Copy Markdown

The WeightSynchronizer FFI derived the host staging slot as shard_idx % num_shards, which only works if a slice's device ordinals are contiguous and aligned to a multiple of num_shards. Device ordinals are not guaranteed to be, so pass the staging slot explicitly as a range-checked logical_shard_idx input instead of deriving it from the device ordinal.

@google-cla

google-cla Bot commented Jul 21, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@copybara-service copybara-service Bot changed the title The WeightSynchronizer FFI derived the host staging slot as The WeightSynchronizer FFI derived the host staging slot as shard_idx % num_shards, which only works if a slice's device ordinals are contiguous and aligned to a multiple of num_shards. Device ordinals are not guaranteed to be, so pass the staging slot explicitly as a range-checked logical_shard_idx input instead of deriving it from the device ordinal. Jul 21, 2026
…x % num_shards`, which only works if a slice's device ordinals are contiguous and aligned to a multiple of `num_shards`. Device ordinals are not guaranteed to be, so pass the staging slot explicitly as a range-checked `logical_shard_idx` input instead of deriving it from the device ordinal.

PiperOrigin-RevId: 951205209
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants