-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Add caching for _rename_without_collisions
#158594
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
Add caching for _rename_without_collisions
#158594
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/158594
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ✅ You can merge normally! (1 Unrelated Failure)As of commit 309f0dc with merge base ee09928 ( UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
Rename the nodes so that anything that is renamed is strictly increasing. This means gaps in suffixes are allowed.
|
@pianpwk Can you take another look when you have time? Thanks |
@pianpwk What else do I need to do to get this PR merged in?
|
@hsjts0u running the PR on internal tests looks good, I'll merge this internal-first. Nothing needed from your side right now. |
|
@pytorchbot merge (Initiating merge automatically since Phabricator Diff has merged) |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). 8000 p> Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Fixes #158357