Skip to content

Fix xla::Future mapped callback completion drop-off across pip-wheel .so boundary - #480

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

Fix xla::Future mapped callback completion drop-off across pip-wheel .so boundary#480
copybara-service[bot] wants to merge 1 commit into
mainfrom
test_955977043

Conversation

@copybara-service

Copy link
Copy Markdown

Fix xla::Future mapped callback completion drop-off across pip-wheel .so boundary

Capture copy_future by value in the .Map(...) closure in weight_synchronizer_base.cc (D2h) to preserve AsyncValue reference counting across dynamic library (.so) boundaries without dropping completion signals or hanging execution.

….so boundary

Capture copy_future by value in the .Map(...) closure in weight_synchronizer_base.cc (D2h) to preserve AsyncValue reference counting across dynamic library (.so) boundaries without dropping completion signals or hanging execution.

PiperOrigin-RevId: 955977043
@google-cla

google-cla Bot commented Jul 29, 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.

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