-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
Support Room kotlin gencode #630
Conversation
updated Room lib, kotlin version and compiler added new test to the repo
added new Room classes (generated through ksp) to VisitorTest
fixed imports moved VisitorTest classes into specific folder
) { | ||
super.visitMethodInsn(opcode, owner, name, descriptor, isInterface) | ||
// The backend binds the exception to the current span, via tracing without performance, so we don't need any special try/catch management. | ||
if (opcode == Opcodes.INVOKEVIRTUAL) { |
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.
hrm, does INVOKEVIRTUAL
work with the CLOSE
method? It used to be INVOKEINTERFACE
before
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.
nice catch!
I updated the instrumentation to take the method type into consideration and updated the condition for the close method
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.
one point to clarify, but otherwise LGTM!
…n when instrumenting its methods
…ix/room-generate-kotlin
…n when instrumenting its methods
#skip-changelog
📜 Description
removed try catch from room instrumentation, as TWP (Tracing Without Performance) makes it useless
added new Room classes (generated through ksp) to VisitorTest
In order to use new Room version and ksp, i had to update agp, gradle, kotlin, room, sdk and kotlin compiler versions
💡 Motivation and Context
Fixes #585
Also, removing all try/catch management from Room instrumentation makes it simpler and more robust
💚 How did you test it?
Added classes generated with ksp to VisitorTest
📝 Checklist
🔮 Next steps