Rafael Winterhalter

I will try to look into this. In order to debug, it would be necessary to scale down the batch size to avoid that multiple classes are transformed in a...

Thanks a lot. I will have a look!

There is no error in the class file. But it seems that the class file becomes too big and this is what likely fails the instrumentation. This cannot be easily...

Then I think this is likely an issue of agent interaction. If there are some agents that do not support retransformation, and others do, then retransformation will result in verification...

OpenTelemetry uses decoration when instrumenting types: https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/2b42bc24c6cdc5cf456d32e36ba597e99b6a6c8d/javaagent-tooling/src/main/java/io/opentelemetry/javaagent/tooling/AgentInstaller.java#L145 This means that it is not technically possible to change a class file signature from the agent. As a result the verification error...

I might have found a bug while walking through all ASM visitors. Possibly, this is the cause. If you built Byte Buddy master, and then OpenTelemetry, you could try yourself....

I do not think that we can support this. In order to mock methods (static or member), we need to make sure that the object is fully initialized. This means...

The idea is that Mockito only affects mocks. If the class in question already is initialized at the time of calling, nothing would happen as the singelton instance is already...

Mockito also does this and applies this behaviour for example for static methods. I think mokk also allows using this with singeltons, meaning it allows to mock those objects similar...

I consider this a bugfix, not a regression. As explained here: https://github.com/mockito/mockito/issues/3525