Vladimir Sitnikov
Vladimir Sitnikov
Fixed in https://github.com/apache/jmeter/pull/6431
If API level 33 Cleaner is not suitable, then [lazycleaner](https://github.com/juanplopes/lazycleaner) could probably do. In pgjdbc we adopted (we copy-pasted the implementation and changed the package to avoid clashes) https://github.com/pgjdbc/pgjdbc/pull/2847
One more thing: `new Thread` is prone to leaks since OpenJDK leaks `Thread.inheritedAccessControlContext`, so a better JVM solution for Java
@nroduit , the PRs in driver I list serve exactly the same purpose: it replaces old `finalize` method with a custom cleaner. I see you have CustomCleaner, and I am...
Is the issue still relevant? Can you share a reproducer project?
There's a catch on what to do when the time runs out. Should you wait indefinitely? Should you wait for some amount of time? There's a workaround if you use...
Would you please add a test case for the change?
>as defined by Semantic Versioning. If you refer to "Sematic Versining", then it might overcomplicate 0ver specification. In any case, the current state, `"major version" is used without a clear...
Frankly, I find AssertJ assertions are hard to extend. The design of self-referring generic prevents extension methods with custom assertions, so I ended up migrating to Atrium.
It might indeed make sense to split the property in two: "max rows" limit at JDBC level and "number of fetched rows" at the client level.