Ben Manes

Results 82 issues of Ben Manes

The `{@snippet : ...}` is the preferred replacement for `{@code ...}` code blocks. When mirroring the [guava change](https://github.com/google/guava/commit/157b3f7e5ebff7beb6d32d511b8693d759be7d66) I received the following warnings: ``` /Users/ben/projects/caffeine/caffeine/src/main/java/com/github/benmanes/caffeine/cache/Caffeine.java:73: warning: [UnescapedEntity] This looks like...

When enabling NullAway's jspecify mode, the use of arrays needs to be annotated for stricter nullability. For example, ```console .../LocalAsyncCache.java:818: warning: [NullAway] Writing @Nullable expression into array with @NonNull contents....

### Guava Version 33.4.9-SNAPSHOT ### Description I tried to run the pre-release in Caffeine's test suite to verify the [recent fix](https://github.com/google/guava/commit/087f2c4a8012fb1256f80f6f776df0e8706af683) for cache computations (thanks @eamonnmcmanus). Other than different interpretations...

type=defect
status=triaged
package=cache
P3

As an OSGi novice, I was very confused when my tests failed on JDK-25 and the Pax Exam team kindly helped me [resolve](https://github.com/ops4j/org.ops4j.pax.exam/issues/1131#issuecomment-3370313321) that setting the `Require-Capability` explicitly. Since this...

### Current Behavior When upgrading from v9.2.1, the very large Caffeine test suite task [fails](https://github.com/ben-manes/caffeine/actions/runs/19774769531/job/56666449449#step:5:354) to complete. This Gradle release reworked the test suite reporting and I suspect it is...

a:regression
in:test-reporting

**Affects PMD Version:** 7.19.0 **Rule:** EnumComparison **Description:** **Code Sample demonstrating the issue:** This is reproducible as, ```java assertThat(new Object().equals(null)).isFalse(); ``` **Expected outcome:** Only enums should be reported on and null...

a:false-positive

I noticed this interesting [compilation error](https://github.com/be-hase/caffeine-coroutines/pull/56) on a kotlin wrapper for Caffeine when it attempted to upgrade the dependency to the JSpecify annotated version. Here's a cleaned up error message...

When (ab)using parameterized tests to run thousands of times, the execution finishes in a reasonable amount of time. However, the UI report takes much longer to complete. Naively it seems...

I ran a profile to try to understand why my Lincheck tests now take 1 hour to run, which became much worse in the recent releases. There was no smoking...

Thanks for the recent fixes! If [JEP 519: Compact Object Headers](https://openjdk.org/jeps/519) is enabled on JDK-25+ runs, then this impacts the unsafe object offset calculations and can lead to a crash....