You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2026/07/11 04:49:00 UTC
[jira] [Commented] (NIFI-16101) Null Check Method is called with obviously non-null argument
[ https://issues.apache.org/jira/browse/NIFI-16101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18095481#comment-18095481 ]
ASF subversion and git services commented on NIFI-16101:
--------------------------------------------------------
Commit 03f58ff43f0a974adabb14be41b6c45817a46666 in nifi's branch refs/heads/main from dan-s1
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=03f58ff43f0 ]
NIFI-16101 Fixed warnings resulting from Intellij "Null Check Method is called with obviously non-null argument" check. (#11416)
> Null Check Method is called with obviously non-null argument
> ------------------------------------------------------------
>
> Key: NIFI-16101
> URL: https://issues.apache.org/jira/browse/NIFI-16101
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Daniel Stieglitz
> Assignee: Daniel Stieglitz
> Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Running Intellij
> Analyze -> Run Inspection by Name -> Null Check Method is called with obviously non-null argument
> indicates there are 10 places in the code where the argument for assertNotNull or requireNonNull are testing an argument which is not null.
> The purpose of this ticket is to correct those places either by correcting the arguments order or by removing the assertion.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)