- Notifications
You must be signed in to change notification settings - Fork26.3k
Expand docs fornn.functional, and make the wording consistent#148436
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
pytorch-botbot commentedMar 4, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
🔗 Helpful Links🧪 See artifacts and rendered test results athud.pytorch.org/pr/148436
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit80b5039 with merge base1a1a32c ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
linux-foundation-easyclabot commentedMar 4, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
2ad95f4 tof59c238Compare
albanD left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Thanks for take the time to go over this!
albanD commentedApr 9, 2025
@pytorchbot merge -r |
Pull workflow has not been scheduled for the PR yet. It could be because author doesn't have permissions to run those or skip-checks keywords were added to PR/commits, aborting merge. Please get/give approval for the workflows and/or remove skip ci decorators before next merge attempt. If you think this is a mistake, please contact PyTorch Dev Infra. |
olipinski commentedApr 12, 2025
Hi@albanD, it seems the merge won't go through without the labels, but I don't think I can add them myself, so I have requested re-review. |
albanD commentedApr 14, 2025
@pytorchbot merge |
Pull workflow has not been scheduled for the PR yet. It could be because author doesn't have permissions to run those or skip-checks keywords were added to PR/commits, aborting merge. Please get/give approval for the workflows and/or remove skip ci decorators before next merge attempt. If you think this is a mistake, please contact PyTorch Dev Infra. |
huydhn commentedApr 14, 2025
@pytorchbot rebase |
pytorchmergebot commentedApr 14, 2025
@pytorchbot started a rebase job ontorefs/remotes/origin/viable/strict. Check the current statushere |
Fix HuberLoss consistencySigned-off-by: Olaf Lipinski <o.lipinski@soton.ac.uk>
Signed-off-by: Olaf Lipinski <o.lipinski@soton.ac.uk>
pytorchmergebot commentedApr 14, 2025
Successfully rebased |
f59c238 to80b5039Comparehuydhn commentedApr 14, 2025
@pytorchbot merge |
pytorchmergebot commentedApr 14, 2025
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in thewiki. Questions? Feedback? Please reach out to thePyTorch DevX Team |
…orch#148436)Expands the docs for the loss functions, and makes the wording consistent.Fixespytorch#148353Pull Requestresolved:pytorch#148436Approved by:https://github.com/albanD
…orch#148436)Expands the docs for the loss functions, and makes the wording consistent.Fixespytorch#148353Pull Requestresolved:pytorch#148436Approved by:https://github.com/albanD
Expands the docs for the loss functions, and makes the wording consistent.
Fixes#148353