You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Joe Skora <js...@gmail.com> on 2016/02/14 04:58:24 UTC
Re: [jira] [Commented] (NIFI-1513) Fix high impact coverity issues
Is this intended for the 0.5.0 release or just queuing up for 0.5.1?
On Sat, Feb 13, 2016 at 10:48 PM, Joseph Witt (JIRA) <ji...@apache.org>
wrote:
>
> [
> https://issues.apache.org/jira/browse/NIFI-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15146370#comment-15146370
> ]
>
> Joseph Witt commented on NIFI-1513:
> -----------------------------------
>
> happy to review but waiting for my access to coverity defect report so I
> can see the why behind a couple of these. In the Bin/Merge case I *think*
> the issue is related to referencing a volatile member variable twice rather
> than once and thus the value could have changed. Anyway looks like a lot
> of good cleanup
>
> > Fix high impact coverity issues
> > -------------------------------
> >
> > Key: NIFI-1513
> > URL: https://issues.apache.org/jira/browse/NIFI-1513
> > Project: Apache NiFi
> > Issue Type: Improvement
> > Affects Versions: 0.5.0
> > Reporter: Tony Kurc
> > Assignee: Tony Kurc
> > Priority: Minor
> >
> > Coverity Scan discovered a few issues, this is a ticket to track
> progress on mitigating them
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>
Re: [jira] [Commented] (NIFI-1513) Fix high impact coverity issues
Posted by Tony Kurc <tr...@gmail.com>.
Not 0.5.0! The issues, as you can probably tell from the pr I submitted,
are unlikely to have catastrophic effect. Potential resource leaks and some
sort of false alarm threading issues were the top 4.
On Feb 13, 2016 10:58 PM, "Joe Skora" <js...@gmail.com> wrote:
> Is this intended for the 0.5.0 release or just queuing up for 0.5.1?
>
> On Sat, Feb 13, 2016 at 10:48 PM, Joseph Witt (JIRA) <ji...@apache.org>
> wrote:
>
> >
> > [
> >
> https://issues.apache.org/jira/browse/NIFI-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15146370#comment-15146370
> > ]
> >
> > Joseph Witt commented on NIFI-1513:
> > -----------------------------------
> >
> > happy to review but waiting for my access to coverity defect report so I
> > can see the why behind a couple of these. In the Bin/Merge case I
> *think*
> > the issue is related to referencing a volatile member variable twice
> rather
> > than once and thus the value could have changed. Anyway looks like a lot
> > of good cleanup
> >
> > > Fix high impact coverity issues
> > > -------------------------------
> > >
> > > Key: NIFI-1513
> > > URL: https://issues.apache.org/jira/browse/NIFI-1513
> > > Project: Apache NiFi
> > > Issue Type: Improvement
> > > Affects Versions: 0.5.0
> > > Reporter: Tony Kurc
> > > Assignee: Tony Kurc
> > > Priority: Minor
> > >
> > > Coverity Scan discovered a few issues, this is a ticket to track
> > progress on mitigating them
> >
> >
> >
> > --
> > This message was sent by Atlassian JIRA
> > (v6.3.4#6332)
> >
>