Remove @NullUnmarked workaround for NullAway bug on generic types · micrometer-metrics/micrometer#6404

2025-06-14T00:09:08.000Z

It seems ` ` does not work well in some situations, see https://github.com/uber/NullAway/issues/1075. Because of this bug in NullAway, we need to use `@NullUnmarked` and "invert" the contract unnecessarily, see [here](https://github.com/micrometer-metrics/micrometer/pull/6385/files#diff-ded137c872c542917642b07bf544b3c5d4319a17a2f10fe771bf158f54390c11R59) and [here](https://github.com/micrometer-metrics/micrometer/pull/6385/files#diff-ded137c872c542917642b07bf544b3c5d4319a17a2f10fe771bf158f54390c11R72-R73).

(4 留言) (0 反應) (0 負責人)Java (4,220 star) (935 fork)batch import

help wantednullabilitypolishtype: task

描述

It seems <T extends @Nullable Object> does not work well in some situations, see https://github.com/uber/NullAway/issues/1075.

Because of this bug in NullAway, we need to use @NullUnmarked and "invert" the contract unnecessarily, see here and here.

貢獻者指南

技術棧: java
領域: tooling
議題類型: refactor
難度: 3
預計時間: 1-3 hours
活動狀態: blocked
清晰度: clear
前置要求: JavaNullAwayGenerics
新手友善度: 60
研究方向: Examine the referenced PR #6385 and the specific lines where @NullUnmarked is used (see diff links in issue). Monitor the NullAway issue #1075 for the upstream fix. Once the NullAway bug is resolved, remove the @NullUnmarked annotations and revert the inverted contract. Update any relevant tests to ensure correctness without the workaround.