Skip to content

Conversation

@zou3519
Copy link
Contributor

@zou3519 zou3519 commented Sep 7, 2022

Stack from ghstack (oldest at bottom):

It was based off of the Python op registration API that has been
implemented in PyTorch already, so we can always bring it back, but
we're probably taking a different approach here.

Test Plan:

  • tests

Differential Revision: D39315050

It was based off of the Python op registration API that has been
implemented in PyTorch already, so we can always bring it back, but
we're probably taking a different approach here.

Test Plan:
- tests

[ghstack-poisoned]
@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Sep 7, 2022

🔗 Helpful links

✅ No Failures (20 Pending)

As of commit cbdac93 (more details on the Dr. CI page):

Expand to see more

💚 💚 Looks good so far! There are no failures yet. 💚 💚


This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

It was based off of the Python op registration API that has been
implemented in PyTorch already, so we can always bring it back, but
we're probably taking a different approach here.

Test Plan:
- tests

[ghstack-poisoned]
It was based off of the Python op registration API that has been
implemented in PyTorch already, so we can always bring it back, but
we're probably taking a different approach here.

Test Plan:
- tests

[ghstack-poisoned]
It was based off of the Python op registration API that has been
implemented in PyTorch already, so we can always bring it back, but
we're probably taking a different approach here.

Test Plan:
- tests

[ghstack-poisoned]
@zou3519
Copy link
Contributor Author

zou3519 commented Sep 7, 2022

@zou3519 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

from functorch.experimental import functionalize

if not IS_WINDOWS:
from functorch._src.custom_function import custom_vjp
Copy link
Contributor

@samdow samdow Sep 7, 2022

Choose a reason for hiding this comment

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

Do we want to get rid of the file "functorch/_src/custom_function.py" too?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good catch, yes

It was based off of the Python op registration API that has been
implemented in PyTorch already, so we can always bring it back, but
we're probably taking a different approach here.

Test Plan:
- tests

Differential Revision: [D39315050](https://our.internmc.facebook.com/intern/diff/D39315050)

[ghstack-poisoned]
@pytorch-bot
Copy link

pytorch-bot bot commented Sep 7, 2022

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/84638

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 03aa4d3:
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@zou3519
Copy link
Contributor Author

zou3519 commented Sep 7, 2022

@zou3519 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@zou3519 zou3519 added the test-config/functorch Use this label to run only functorch tests label Sep 7, 2022
It was based off of the Python op registration API that has been
implemented in PyTorch already, so we can always bring it back, but
we're probably taking a different approach here.

Test Plan:
- tests

Differential Revision: [D39315050](https://our.internmc.facebook.com/intern/diff/D39315050)

[ghstack-poisoned]
@zou3519 zou3519 removed the test-config/functorch Use this label to run only functorch tests label Sep 8, 2022
It was based off of the Python op registration API that has been
implemented in PyTorch already, so we can always bring it back, but
we're probably taking a different approach here.

Test Plan:
- tests

Differential Revision: [D39315050](https://our.internmc.facebook.com/intern/diff/D39315050)

[ghstack-poisoned]
facebook-github-bot pushed a commit to pytorch/functorch that referenced this pull request Sep 8, 2022
Summary:
X-link: pytorch/pytorch#84638

It was based off of the Python op registration API that has been
implemented in PyTorch already, so we can always bring it back, but
we're probably taking a different approach here.
ghstack-source-id: 166807991

Reviewed By: samdow

Differential Revision: D39315050

Pulled By: zou3519

fbshipit-source-id: 9831cdea0e6401d89137811104f463094b6bca3f
@facebook-github-bot
Copy link
Contributor

@pytorchbot merge

(Initiating merge automatically since Phabricator Diff has merged)

@pytorchmergebot
Copy link
Collaborator

@pytorchbot successfully started a merge job. Check the current status here.
The merge job was triggered without a flag. This means that your change will be merged once all checks on your PR have passed (ETA: 0-4 Hours). If this is not the intended behavior, feel free to use some of the other merge options in the wiki.
Please reach out to the PyTorch DevX Team with feedback or questions!

@github-actions
Copy link
Contributor

github-actions bot commented Sep 8, 2022

Hey @zou3519.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

facebook-github-bot pushed a commit that referenced this pull request Sep 9, 2022
Summary:
Pull Request resolved: #84638

It was based off of the Python op registration API that has been
implemented in PyTorch already, so we can always bring it back, but
we're probably taking a different approach here.
ghstack-source-id: 166807991

Test Plan: - tests

Reviewed By: samdow

Differential Revision: D39315050

Pulled By: zou3519

fbshipit-source-id: 9831cdea0e6401d89137811104f463094b6bca3f
@facebook-github-bot facebook-github-bot deleted the gh/zou3519/495/head branch September 12, 2022 14:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants