-
Notifications
You must be signed in to change notification settings - Fork 39
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
Beeline tracing decorator does preserve function signature #197
Comments
Hey @jwelch92 - thanks for the bug report. I've read through the issue and linked blog post and understand the problem - I really appreciated the links 👍🏻 I was going to suggest that you try instrumenting with OpenTelemetry Python - but as you can see they also use functools.wraps. I think we need to do additional testing, but wrapt feels like the most concise fix and by virtue does support Python 2.7 which is a consideration for us where we try to support older versions of Python util something breaks. Thanks for your PR to help with that process. |
Hello, If this issue is important to you, please feel free to ping here and we can discuss/re-open. |
I am running into essentially this same issue but specifically found the I haven't looked at whether the OpenTelemetry client fixes this or not, but we are unable to do that upgrade at the moment. For anyone else finding this in the future we were able to replace all usages of
|
Versions
Steps to reproduce
Code snippet showing the issue
With output
Additional context
I am using beeline for tracing a Slack application that is using Slack Bolt which uses kwargs injection for handlers. This uses
inspect.getfullargspec
in order to get the list of arguments to inject as seen here.This might not be an issue if I could reorder the decorators but unfortunately due to some constraints imposed by Bolt that's not currently possible so I am looking to fix the decorator behavior in beeline.
Good resource on decorators that I leaned on for narrowing down this issue: https://hynek.me/articles/decorators/.
The text was updated successfully, but these errors were encountered: