Skip to content

Conversation

@tushar00jain
Copy link
Contributor

Differential Revision: D86343575

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Meta Open Source bot. label Nov 7, 2025
@meta-codesync
Copy link

meta-codesync bot commented Nov 7, 2025

@tushar00jain has exported this pull request. If you are a Meta employee, you can view the originating Diff in D86343575.

tushar00jain added a commit to tushar00jain/torchft that referenced this pull request Nov 7, 2025
Summary: Pull Request resolved: meta-pytorch#290

Differential Revision: D86343575
tushar00jain added a commit to tushar00jain/torchft that referenced this pull request Nov 7, 2025
Summary: Pull Request resolved: meta-pytorch#290

Differential Revision: D86343575
tushar00jain added a commit to tushar00jain/torchft that referenced this pull request Nov 7, 2025
Summary: Pull Request resolved: meta-pytorch#290

Differential Revision: D86343575
tushar00jain added a commit to tushar00jain/torchft that referenced this pull request Nov 7, 2025
Summary: Pull Request resolved: meta-pytorch#290

Differential Revision: D86343575
tushar00jain added a commit to tushar00jain/torchft that referenced this pull request Nov 10, 2025
Summary: Pull Request resolved: meta-pytorch#290

Differential Revision: D86343575
tushar00jain added a commit to tushar00jain/torchft that referenced this pull request Nov 10, 2025
Summary:

- add torchcomms integration
- instsall torchcomms in build files
- add a class that wraps torchcomms to offer reconfiguration and timeout handline just like process group wrapper
- allow users to pass either torchcomms or pg to manager -- manager infers the type and calls the relevant api's
- had to work around torchcomms not having get_future api -- since futures are lazy in manager, we can just creae a dummy future and set the value on it since we modify the vlaue in place

Differential Revision: D86343575
tushar00jain added a commit to tushar00jain/torchft that referenced this pull request Nov 10, 2025
Summary:

- add torchcomms integration
- instsall torchcomms in build files
- add a class that wraps torchcomms to offer reconfiguration and timeout handline just like process group wrapper
- allow users to pass either torchcomms or pg to manager -- manager infers the type and calls the relevant api's
- had to work around torchcomms not having get_future api -- since futures are lazy in manager, we can just creae a dummy future and set the value on it since we modify the vlaue in place

Differential Revision: D86343575
tushar00jain added a commit to tushar00jain/torchft that referenced this pull request Nov 11, 2025
Summary:

- add torchcomms integration
- instsall torchcomms in build files
- add a class that wraps torchcomms to offer reconfiguration and timeout handline just like process group wrapper
- allow users to pass either torchcomms or pg to manager -- manager infers the type and calls the relevant api's
- had to work around torchcomms not having get_future api -- since futures are lazy in manager, we can just creae a dummy future and set the value on it since we modify the vlaue in place

Differential Revision: D86343575
tushar00jain added a commit to tushar00jain/torchft that referenced this pull request Nov 11, 2025
Summary:

- add torchcomms integration
- instsall torchcomms in build files
- add a class that wraps torchcomms to offer reconfiguration and timeout handline just like process group wrapper
- allow users to pass either torchcomms or pg to manager -- manager infers the type and calls the relevant api's
- had to work around torchcomms not having get_future api -- since futures are lazy in manager, we can just creae a dummy future and set the value on it since we modify the vlaue in place

Differential Revision: D86343575
Summary:

- add torchcomms integration
- instsall torchcomms in build files
- add a class that wraps torchcomms to offer reconfiguration and timeout handline just like process group wrapper
- allow users to pass either torchcomms or pg to manager -- manager infers the type and calls the relevant api's
- had to work around torchcomms not having get_future api -- since futures are lazy in manager, we can just creae a dummy future and set the value on it since we modify the vlaue in place

Differential Revision: D86343575
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. fb-exported meta-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant