Skip to content

fix stream dependencies in callbacks #246

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 1, 2025
Merged

Conversation

tushar00jain
Copy link
Contributor

@tushar00jain tushar00jain commented Jul 26, 2025

Summary:

  • call future.wait in callbacks to make sure the continuation executes after the future has completed
  • set the stream correctly to execute callback scheduled by bucketized allreduce

Stack created with Sapling. Best reviewed with ReviewStack.

Summary:
use http transport instead of pg transport -- pg transport fails to resolve address when running locally
Copy link
Member

@d4l3k d4l3k left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@tushar00jain tushar00jain force-pushed the pr246 branch 6 times, most recently from c6d1cdb to 4893f67 Compare July 29, 2025 03:37
@tushar00jain tushar00jain force-pushed the pr246 branch 11 times, most recently from 43dd4fb to 17ac343 Compare July 31, 2025 02:47
Summary:
- call future.wait in callbacks to make sure the continuation executes after the future has completed
- set the stream correctly to execute callback scheduled by bucketized allreduce
@tushar00jain tushar00jain merged commit c133307 into pytorch:main Aug 1, 2025
17 of 19 checks passed
@tushar00jain tushar00jain deleted the pr246 branch August 1, 2025 05:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Meta Open Source bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants