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
[FX] Make wrapped functions traceable #46692
Conversation
[ghstack-poisoned]
This patch does two things: 1. For the purpose of introspecting arguments, this patch adds a call to `inspect.unwrap` to unwrap any layers of `functools.wraps` decorators on the function. This is similar to what `inspect.signature` is doing as well. This allows for functions/methods with wrapping decorators applied to them to be traced 2. Fixes a poor error message where a variadic method without an explicit `self` argument was trying to be traced. I elected to just throw in this case for now. Conceptually we could support this but I was running into some weird correctness issues and I think that's better addressed in a follow-up PR. Closes #46665 Differential Revision: [D24465958](https://our.internmc.facebook.com/intern/diff/D24465958) [ghstack-poisoned]
This patch does two things: 1. For the purpose of introspecting arguments, this patch adds a call to `inspect.unwrap` to unwrap any layers of `functools.wraps` decorators on the function. This is similar to what `inspect.signature` is doing as well. This allows for functions/methods with wrapping decorators applied to them to be traced 2. Fixes a poor error message where a variadic method without an explicit `self` argument was trying to be traced. I elected to just throw in this case for now. Conceptually we could support this but I was running into some weird correctness issues and I think that's better addressed in a follow-up PR. Closes #46665 Differential Revision: [D24465958](https://our.internmc.facebook.com/intern/diff/D24465958) [ghstack-poisoned]
💊 CI failures summary and remediationsAs of commit c63c90a (more details on the Dr. CI page): ✅ None of the CI failures appear to be your fault 💚
🚧 1 ongoing upstream failure:These were probably caused by upstream breakages that are not fixed yet:
This comment was automatically generated by Dr. CI (expand for details).Follow this link to opt-out of these comments for your Pull Requests.Please report bugs/suggestions on the GitHub issue tracker or post in the (internal) Dr. CI Users group. This comment has been revised 3 times. |
ghstack-source-id: 97c7d1b97ed9a6e54dacfe032ea7871820c150b7 Pull Request resolved: #46692
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.
Magic
@jamesr66a merged this pull request in 9ccf85b. |
Stack from ghstack:
This patch does two things:
inspect.unwrap
to unwrap any layers offunctools.wraps
decorators on the function. This is similar to whatinspect.signature
is doing as well. This allows for functions/methods with wrapping decorators applied to them to be tracedself
argument was trying to be traced. I elected to just throw in this case for now. Conceptually we could support this but I was running into some weird correctness issues and I think that's better addressed in a follow-up PR.Closes #46665
Differential Revision: D24465958