micrometer-metrics/micrometer

Remove @NullUnmarked workaround for NullAway bug on generic types

Open

#6,404 创建于 2025年6月14日

在 GitHub 查看
 (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
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
blocked
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
JavaNullAwayGenerics
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
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.