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
[1.8] Instrumentation compatibility #1429
Comments
Hi, thanks for opening this issue! Yes, I intend to maintain compatibility. Right now, GitHub is running class-based types and lot of different instrumenters. Let me share some implementation details and maybe the cause of the issue will present itself ...
By the way, regarding Sometime, execution will use the classes instead of |
Maybe the thing to do is add an instrumenter to |
Thank you for your reply!
Are you still planning to do that? :) |
Yes, 1.9-dev branch has a new runtime that uses class-based types only, although in a few cases it's still supported by the compatibility layer. Hoping to remove that too, but not quite there yet! |
Removing the compat layer is WIP in #2363 , closing this issue as it doesn't have any specific work to do. |
Hey!
I have 2 issues when I'm trying to instrument fields by using the
1.8-dev
branch:For example, I have the following code in my app:
When I'm trying to introspect a field, I'm getting the following:
When I'm trying to redefine the
resolve_proc
, it passes the following:Are you planning to keep the instrumentation compatible with the previous gem versions? :)
The text was updated successfully, but these errors were encountered: