Marc R. Hoffmann

Due to JVM spec this seems to be allowed (even if not emitted by javac or other compilers we're testing).

Out of curiosity: What was the original source code of the method? What is the purpose of 0: iload_0 1: i2l 2: lstore_0 when the long value is not used...

Overwriting variables is not a problem as such. The issue seems to be specific to the situation where the last slot used by method parameters is overwritten with a two...

@Godin My concern with my proposal also was runtime overhead (increased locals). Not sure though what the overhead with a typical code base would be.

@bvella We implemented approach 1) in #893. Can you please test this whether it works for your scenario? You either build the branch yourself of find the corresponding build here:...

Well this is the standard way how lists are configured in Maven. I don't think we should change the existing API. Do you have a proposal how to fix this...

@amaembo @Godin We need to consider that JaCoCo cannot handle different versions of the same class file in the same report (group). Typically multirelease JARs will have different versions of...

@amaembo Even if there is a single name clash and two versions of a class with the same name will be provided JaCoCo report generation will fail.

I agree with @Godin that we should not try to target this in JaCoCo for now.

This is obviously due to the change described here: https://aws.amazon.com/blogs/compute/coming-soon-expansion-of-aws-lambda-states-to-all-functions/ If you specify multiple properties (like `image_uri` and `memory_size`) the tool probably internally issues multiple subsequent requests which fail due...