Rafael Winterhalter
Rafael Winterhalter
This is not a deliberate change. I remember that Kotlin does something with marker types (being package private) that is not normally compilable in Java. Let me find out why...
I do not quite understand what changed yet, but you should always set: `new ByteBuddy().with(TypeValidation.DISABLED)` in non-debugging scenarios for performance reason. Without this validation, the invisibility will also be ignored.
I added a dependency management to the test project that forces use of BB 1.12.13 instead and the same error occurs. But there is indeed an inconsistency in Byte Buddy...
Ah, version dot-3, not dot-13. I'll look into that.
Yes, this is already fixed on master and I can confirm that it works with `1.12.14-SNAPSHOT`. It's the mentioned inconsistency with handling the default package which should be resolved with...
It's because Java 17 is strict on the module boundaries and reflection is no longer supported to do this. This exception is expected. The agent should rather use `ClassInjector.UsingLookup`. This...
This is a JVM crash. Did you get a crashdump file?
The dump suggests that the garbage collection failed somewhere. There's no Byte Buddy frames in the stack.
Have you tried registering an `AgentBuilder.Listener` to see if an exception is thrown?
It seems like `junction` captures that field instrumentation. Try switching the two interceptions definitions.