-
Bug
-
Resolution: Fixed
-
Minor
-
None
Remoting versions since 3.11 have explicit annotations for Channel#getCurrent(), and there are lots of FindBugs issues reported due to that. All usages are safe, so there is no need in backporting.
My proposal is to...
1) Add a convenience default method to Remoting's Callable, which throws IOException
2) Use the new convenience method in all Callable implementations in the core
[JENKINS-48055] FindBugs: Channel#current() may return null, not all routines in the core handle that
Epic Link | New: JENKINS-36716 [ 172750 ] |
Description |
New:
Remoting versions since 3.11 have explicit annotations for Channel#getCurrent(), and there are lots of FindBugs issues reported due to that. All usages are safe, so there is no need in backporting. My proposal is to... 1) Add a convenience default method to Remoting's Callable, which throws IOException 2) Use the new convenience method in all Callable implementations in the core |
Assignee | New: Oleg Nenashev [ oleg_nenashev ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Component/s | New: remoting [ 15489 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |