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 Percivall <jo...@yahoo.com.INVALID> on 2016/08/26 16:25:19 UTC
[VOTE] Release Apache NiFi 1.0.0 (RC1)
Hello Apache NiFi Community,
I am pleased to be calling this vote for the source release of Apache NiFi,
nifi-1.0.0.
The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1090/
Note: There is a second binary being distributed now, the NiFi Toolkit. It
can be used to facilitate securing a NiFi instance.
The Git tag is nifi-1.0.0-RC1
The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
* https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=74d5224783dfdc513f6b3ad5ed96671d3c581707
* https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3ad5ed96671d3c581707
Checksums of nifi-1.0.0-source-release.zip:
MD5: 8bdba49a73b94d036fad6c63b0ebe39d
SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92
Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/jpercivall
KEYS file available here:
https://dist.apache.org/repos/dist/release/nifi/KEYS
595 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12332640
Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.0.0
The vote will be open for 72 hours.
Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, and test. Then
please vote:
[ ] +1 Release this package as nifi-1.0.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...
Thanks!
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Matt Burgess <ma...@gmail.com>.
+1 (non-binding)
Verified checksums, GPG signature, commit hash, LICENSE/README/NOTICE,
etc. Tested various flows, templates, controller services on unsecure
standalone and secure 3-node cluster, looking good!
On Fri, Aug 26, 2016 at 12:25 PM, Joe Percivall
<jo...@yahoo.com.invalid> wrote:
> Hello Apache NiFi Community,
>
> I am pleased to be calling this vote for the source release of Apache NiFi,
> nifi-1.0.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1090/
>
> Note: There is a second binary being distributed now, the NiFi Toolkit. It
> can be used to facilitate securing a NiFi instance.
>
> The Git tag is nifi-1.0.0-RC1
> The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=74d5224783dfdc513f6b3ad5ed96671d3c581707
> * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3ad5ed96671d3c581707
>
> Checksums of nifi-1.0.0-source-release.zip:
> MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/jpercivall
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 595 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12332640
>
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.0.0
>
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test. Then
> please vote:
>
> [ ] +1 Release this package as nifi-1.0.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> Thanks!
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by James Wing <jv...@gmail.com>.
+1 (non-binding). I ran through the release helper, including hashes,
build, tests. No showstopping issues for me.
James
On Fri, Aug 26, 2016 at 9:25 AM, Joe Percivall <
joepercivall@yahoo.com.invalid> wrote:
> Hello Apache NiFi Community,
>
> I am pleased to be calling this vote for the source release of Apache NiFi,
> nifi-1.0.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1090/
>
> Note: There is a second binary being distributed now, the NiFi Toolkit. It
> can be used to facilitate securing a NiFi instance.
>
> The Git tag is nifi-1.0.0-RC1
> The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> 74d5224783dfdc513f6b3ad5ed96671d3c581707
> * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3ad5ed9667
> 1d3c581707
>
> Checksums of nifi-1.0.0-source-release.zip:
> MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/jpercivall
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 595 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12316020&version=12332640
>
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/
> Release+Notes#ReleaseNotes-Version1.0.0
>
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test. Then
> please vote:
>
> [ ] +1 Release this package as nifi-1.0.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> Thanks!
>
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Alan Jackoway <al...@cloudera.com>.
Builds with JDK 1.8.0_60 so I am a +0 in total. It's been a long time
(maybe 0.5?) since I attempted a full nifi build rather than just building
the processors I am working with. It seems like some time in that window a
JDK incompatibility was introduced.
On Mon, Aug 29, 2016 at 2:58 PM, Alan Jackoway <al...@cloudera.com> wrote:
> -1 (non-binding) from me, but likely an issue on my machine.
>
> I get a compile error in nifi-framework-cluster on this release and master
> using an empty maven repository.
>
> Mac OS X 10.10.5. Maven 3.2.5. Oracle Java 1.8.0_31
>
> The end of maven debug output (which doesn't even say which file is
> failing to compile) is at https://gist.github.com/jackowaya/
> 25a8f184089335b1eed14f00cbb5f36b if you're interested.
>
> I'm going to try a more recent JDK next.
>
> Alan
>
> On Mon, Aug 29, 2016 at 2:38 PM, Jeff <jt...@gmail.com> wrote:
>
>> Still voting a +1 for the release, but I recently created two JIRAs for
>> the
>> issues I encountered while testing nifi-1.0.0-RC1:
>>
>> https://issues.apache.org/jira/browse/NIFI-2695 - Access Denied messages
>> should include more information
>> https://issues.apache.org/jira/browse/NIFI-2699 - Improve handling of
>> response timeouts in cluster
>>
>> On Mon, Aug 29, 2016 at 1:59 PM Matt Gilman <ma...@gmail.com>
>> wrote:
>>
>> > +1 (binding)
>> >
>> > Verified keys, hashes, build, etc. Ran standalone and cluster secured
>> > instances.
>> >
>> > Evaluated the issues Koji reported and created two minor JIRAs [1] [2]
>> to
>> > perform some additional clean up in the next release.
>> >
>> > Thanks, Joe P!
>> >
>> > Matt
>> >
>> > [1] https://issues.apache.org/jira/browse/NIFI-2694
>> > [2] https://issues.apache.org/jira/browse/NIFI-2697
>> >
>> > On Mon, Aug 29, 2016 at 1:21 PM, Mark Payne <ma...@hotmail.com>
>> wrote:
>> >
>> > > +1 (binding)
>> > >
>> > > Verified the keys & md5 hash. Was able to startup the node and verify
>> > > things are behaving as expected.
>> > > Verified that the README, NOTICE, and LICENSE files exist and appear
>> to
>> > be
>> > > correct.
>> > >
>> > > Thanks for pulling this together, Joe P!
>> > >
>> > > > On Aug 26, 2016, at 12:25 PM, Joe Percivall <joepercivall@yahoo.com
>> > .INVALID>
>> > > wrote:
>> > > >
>> > > > Hello Apache NiFi Community,
>> > > >
>> > > > I am pleased to be calling this vote for the source release of
>> Apache
>> > > NiFi,
>> > > > nifi-1.0.0.
>> > > >
>> > > > The source zip, including signatures, digests, etc. can be found at:
>> > > > https://repository.apache.org/content/repositories/orgapache
>> nifi-1090/
>> > > >
>> > > > Note: There is a second binary being distributed now, the NiFi
>> Toolkit.
>> > > It
>> > > > can be used to facilitate securing a NiFi instance.
>> > > >
>> > > > The Git tag is nifi-1.0.0-RC1
>> > > > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
>> > > > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
>> > > 74d5224783dfdc513f6b3ad5ed96671d3c581707
>> > > > * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3a
>> d5ed9667
>> > > 1d3c581707
>> > > >
>> > > > Checksums of nifi-1.0.0-source-release.zip:
>> > > > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
>> > > > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
>> > > > SHA256:
>> > 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92
>> > > >
>> > > > Release artifacts are signed with the following key:
>> > > > https://people.apache.org/keys/committer/jpercivall
>> > > >
>> > > > KEYS file available here:
>> > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
>> > > >
>> > > > 595 issues were closed/resolved for this release:
>> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> > > projectId=12316020&version=12332640
>> > > >
>> > > > Release note highlights can be found here:
>> > > > https://cwiki.apache.org/confluence/display/NIFI/
>> > > Release+Notes#ReleaseNotes-Version1.0.0
>> > > >
>> > > > The vote will be open for 72 hours.
>> > > > Please download the release candidate and evaluate the necessary
>> items
>> > > > including checking hashes, signatures, build from source, and test.
>> > Then
>> > > > please vote:
>> > > >
>> > > > [ ] +1 Release this package as nifi-1.0.0
>> > > > [ ] +0 no opinion
>> > > > [ ] -1 Do not release this package because...
>> > > >
>> > > > Thanks!
>> > >
>> > >
>> >
>>
>
>
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Alan Jackoway <al...@cloudera.com>.
-1 (non-binding) from me, but likely an issue on my machine.
I get a compile error in nifi-framework-cluster on this release and master
using an empty maven repository.
Mac OS X 10.10.5. Maven 3.2.5. Oracle Java 1.8.0_31
The end of maven debug output (which doesn't even say which file is failing
to compile) is at
https://gist.github.com/jackowaya/25a8f184089335b1eed14f00cbb5f36b if
you're interested.
I'm going to try a more recent JDK next.
Alan
On Mon, Aug 29, 2016 at 2:38 PM, Jeff <jt...@gmail.com> wrote:
> Still voting a +1 for the release, but I recently created two JIRAs for the
> issues I encountered while testing nifi-1.0.0-RC1:
>
> https://issues.apache.org/jira/browse/NIFI-2695 - Access Denied messages
> should include more information
> https://issues.apache.org/jira/browse/NIFI-2699 - Improve handling of
> response timeouts in cluster
>
> On Mon, Aug 29, 2016 at 1:59 PM Matt Gilman <ma...@gmail.com>
> wrote:
>
> > +1 (binding)
> >
> > Verified keys, hashes, build, etc. Ran standalone and cluster secured
> > instances.
> >
> > Evaluated the issues Koji reported and created two minor JIRAs [1] [2] to
> > perform some additional clean up in the next release.
> >
> > Thanks, Joe P!
> >
> > Matt
> >
> > [1] https://issues.apache.org/jira/browse/NIFI-2694
> > [2] https://issues.apache.org/jira/browse/NIFI-2697
> >
> > On Mon, Aug 29, 2016 at 1:21 PM, Mark Payne <ma...@hotmail.com>
> wrote:
> >
> > > +1 (binding)
> > >
> > > Verified the keys & md5 hash. Was able to startup the node and verify
> > > things are behaving as expected.
> > > Verified that the README, NOTICE, and LICENSE files exist and appear to
> > be
> > > correct.
> > >
> > > Thanks for pulling this together, Joe P!
> > >
> > > > On Aug 26, 2016, at 12:25 PM, Joe Percivall <joepercivall@yahoo.com
> > .INVALID>
> > > wrote:
> > > >
> > > > Hello Apache NiFi Community,
> > > >
> > > > I am pleased to be calling this vote for the source release of Apache
> > > NiFi,
> > > > nifi-1.0.0.
> > > >
> > > > The source zip, including signatures, digests, etc. can be found at:
> > > > https://repository.apache.org/content/repositories/
> orgapachenifi-1090/
> > > >
> > > > Note: There is a second binary being distributed now, the NiFi
> Toolkit.
> > > It
> > > > can be used to facilitate securing a NiFi instance.
> > > >
> > > > The Git tag is nifi-1.0.0-RC1
> > > > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > > 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > > * https://github.com/apache/nifi/commit/
> 74d5224783dfdc513f6b3ad5ed9667
> > > 1d3c581707
> > > >
> > > > Checksums of nifi-1.0.0-source-release.zip:
> > > > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> > > > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> > > > SHA256:
> > 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92
> > > >
> > > > Release artifacts are signed with the following key:
> > > > https://people.apache.org/keys/committer/jpercivall
> > > >
> > > > KEYS file available here:
> > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > >
> > > > 595 issues were closed/resolved for this release:
> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > projectId=12316020&version=12332640
> > > >
> > > > Release note highlights can be found here:
> > > > https://cwiki.apache.org/confluence/display/NIFI/
> > > Release+Notes#ReleaseNotes-Version1.0.0
> > > >
> > > > The vote will be open for 72 hours.
> > > > Please download the release candidate and evaluate the necessary
> items
> > > > including checking hashes, signatures, build from source, and test.
> > Then
> > > > please vote:
> > > >
> > > > [ ] +1 Release this package as nifi-1.0.0
> > > > [ ] +0 no opinion
> > > > [ ] -1 Do not release this package because...
> > > >
> > > > Thanks!
> > >
> > >
> >
>
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Jeff <jt...@gmail.com>.
Still voting a +1 for the release, but I recently created two JIRAs for the
issues I encountered while testing nifi-1.0.0-RC1:
https://issues.apache.org/jira/browse/NIFI-2695 - Access Denied messages
should include more information
https://issues.apache.org/jira/browse/NIFI-2699 - Improve handling of
response timeouts in cluster
On Mon, Aug 29, 2016 at 1:59 PM Matt Gilman <ma...@gmail.com> wrote:
> +1 (binding)
>
> Verified keys, hashes, build, etc. Ran standalone and cluster secured
> instances.
>
> Evaluated the issues Koji reported and created two minor JIRAs [1] [2] to
> perform some additional clean up in the next release.
>
> Thanks, Joe P!
>
> Matt
>
> [1] https://issues.apache.org/jira/browse/NIFI-2694
> [2] https://issues.apache.org/jira/browse/NIFI-2697
>
> On Mon, Aug 29, 2016 at 1:21 PM, Mark Payne <ma...@hotmail.com> wrote:
>
> > +1 (binding)
> >
> > Verified the keys & md5 hash. Was able to startup the node and verify
> > things are behaving as expected.
> > Verified that the README, NOTICE, and LICENSE files exist and appear to
> be
> > correct.
> >
> > Thanks for pulling this together, Joe P!
> >
> > > On Aug 26, 2016, at 12:25 PM, Joe Percivall <joepercivall@yahoo.com
> .INVALID>
> > wrote:
> > >
> > > Hello Apache NiFi Community,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > NiFi,
> > > nifi-1.0.0.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1090/
> > >
> > > Note: There is a second binary being distributed now, the NiFi Toolkit.
> > It
> > > can be used to facilitate securing a NiFi instance.
> > >
> > > The Git tag is nifi-1.0.0-RC1
> > > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3ad5ed9667
> > 1d3c581707
> > >
> > > Checksums of nifi-1.0.0-source-release.zip:
> > > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> > > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> > > SHA256:
> 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/jpercivall
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 595 issues were closed/resolved for this release:
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12316020&version=12332640
> > >
> > > Release note highlights can be found here:
> > > https://cwiki.apache.org/confluence/display/NIFI/
> > Release+Notes#ReleaseNotes-Version1.0.0
> > >
> > > The vote will be open for 72 hours.
> > > Please download the release candidate and evaluate the necessary items
> > > including checking hashes, signatures, build from source, and test.
> Then
> > > please vote:
> > >
> > > [ ] +1 Release this package as nifi-1.0.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
> > > Thanks!
> >
> >
>
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Matt Gilman <ma...@gmail.com>.
+1 (binding)
Verified keys, hashes, build, etc. Ran standalone and cluster secured
instances.
Evaluated the issues Koji reported and created two minor JIRAs [1] [2] to
perform some additional clean up in the next release.
Thanks, Joe P!
Matt
[1] https://issues.apache.org/jira/browse/NIFI-2694
[2] https://issues.apache.org/jira/browse/NIFI-2697
On Mon, Aug 29, 2016 at 1:21 PM, Mark Payne <ma...@hotmail.com> wrote:
> +1 (binding)
>
> Verified the keys & md5 hash. Was able to startup the node and verify
> things are behaving as expected.
> Verified that the README, NOTICE, and LICENSE files exist and appear to be
> correct.
>
> Thanks for pulling this together, Joe P!
>
> > On Aug 26, 2016, at 12:25 PM, Joe Percivall <jo...@yahoo.com.INVALID>
> wrote:
> >
> > Hello Apache NiFi Community,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi,
> > nifi-1.0.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1090/
> >
> > Note: There is a second binary being distributed now, the NiFi Toolkit.
> It
> > can be used to facilitate securing a NiFi instance.
> >
> > The Git tag is nifi-1.0.0-RC1
> > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3ad5ed9667
> 1d3c581707
> >
> > Checksums of nifi-1.0.0-source-release.zip:
> > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> > SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/jpercivall
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 595 issues were closed/resolved for this release:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12316020&version=12332640
> >
> > Release note highlights can be found here:
> > https://cwiki.apache.org/confluence/display/NIFI/
> Release+Notes#ReleaseNotes-Version1.0.0
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test. Then
> > please vote:
> >
> > [ ] +1 Release this package as nifi-1.0.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks!
>
>
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Mark Payne <ma...@hotmail.com>.
+1 (binding)
Verified the keys & md5 hash. Was able to startup the node and verify things are behaving as expected.
Verified that the README, NOTICE, and LICENSE files exist and appear to be correct.
Thanks for pulling this together, Joe P!
> On Aug 26, 2016, at 12:25 PM, Joe Percivall <jo...@yahoo.com.INVALID> wrote:
>
> Hello Apache NiFi Community,
>
> I am pleased to be calling this vote for the source release of Apache NiFi,
> nifi-1.0.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1090/
>
> Note: There is a second binary being distributed now, the NiFi Toolkit. It
> can be used to facilitate securing a NiFi instance.
>
> The Git tag is nifi-1.0.0-RC1
> The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=74d5224783dfdc513f6b3ad5ed96671d3c581707
> * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3ad5ed96671d3c581707
>
> Checksums of nifi-1.0.0-source-release.zip:
> MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/jpercivall
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 595 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12332640
>
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.0.0
>
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test. Then
> please vote:
>
> [ ] +1 Release this package as nifi-1.0.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> Thanks!
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Andy LoPresto <al...@apache.org>.
Verified all checksums and GPG signature; verified contrib check and RAT license check; verified git commit ID, checked the LICENSE, README, and NOTICE files, and ran the binary and performed the usual actions within the UI.
I then used the encrypt-config toolkit to encrypt the banner UI text and re-ran the application. Everything checks out.
Mac OS X 10.11.6, JDK 1.8.0_92, Maven 3.3.9
+1 (binding)
Andy LoPresto
alopresto@apache.org
alopresto.apache@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On Aug 28, 2016, at 6:25 PM, Bryan Rosander <br...@gmail.com> wrote:
>
> Downloaded source
>
> Verified checksums
>
> Ran build with contrib-check and empty local repo
>
> Ran build with –T2 concurrency and empty local repo
>
> Used tls-toolkit to generate 4 localhost keystore, truststore,
> nifi.properties and a single client certificate
>
> Started all 4 instances verified no port conflicts, correct certificate
> usage
>
> Imported CA certificate, client cert into browser, verified tls working
> properly
>
> +1 (non-binding)
>
> Thanks,
> Bryan
>
> On Aug 28, 2016 7:30 PM, "Tony Kurc" <tr...@gmail.com> wrote:
>
>> +1 (binding)
>>
>> Full build starting with empty maven repository on Ubuntu 14.04 (x86_64)
>> successfully.
>>
>> Verified signatures and hashes. Reviewed LICENSE/NOTICE.
>>
>> Ran a simple flow with no issues. Ran a few nifi-toolkit commands.
>>
>>
>>
>> On Sun, Aug 28, 2016 at 5:29 PM, Joe Witt <jo...@gmail.com> wrote:
>>
>>> +1 (binding)
>>>
>>> Full clean build w/contrib check good.
>>>
>>> Verified signatures (and strength), hashes, and LICENSE/NOTICE within
>>> sources and convenience binaries.
>>>
>>> Verified the commit the release was based on.
>>>
>>> Ran single and multi-node clusters with favorable results.
>>>
>>> For future release please do move any necessary elements of the UnRar
>>> item to NOTICE where category B items belong. See here for LEGAL
>>> discuss https://issues.apache.org/jira/browse/LEGAL-52 on this.
>>>
>>> Great job pulling the release together again JoeP.
>>>
>>> Thanks
>>> Joe
>>>
>>> On Fri, Aug 26, 2016 at 12:25 PM, Joe Percivall
>>> <jo...@yahoo.com.invalid> wrote:
>>>> Hello Apache NiFi Community,
>>>>
>>>> I am pleased to be calling this vote for the source release of Apache
>>> NiFi,
>>>> nifi-1.0.0.
>>>>
>>>> The source zip, including signatures, digests, etc. can be found at:
>>>> https://repository.apache.org/content/repositories/orgapachenifi-1090/
>>>>
>>>> Note: There is a second binary being distributed now, the NiFi Toolkit.
>>> It
>>>> can be used to facilitate securing a NiFi instance.
>>>>
>>>> The Git tag is nifi-1.0.0-RC1
>>>> The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
>>>> * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
>>> 74d5224783dfdc513f6b3ad5ed96671d3c581707
>>>> * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3ad5ed9667
>>> 1d3c581707
>>>>
>>>> Checksums of nifi-1.0.0-source-release.zip:
>>>> MD5: 8bdba49a73b94d036fad6c63b0ebe39d
>>>> SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
>>>> SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447
>> af92
>>>>
>>>> Release artifacts are signed with the following key:
>>>> https://people.apache.org/keys/committer/jpercivall
>>>>
>>>> KEYS file available here:
>>>> https://dist.apache.org/repos/dist/release/nifi/KEYS
>>>>
>>>> 595 issues were closed/resolved for this release:
>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>>> projectId=12316020&version=12332640
>>>>
>>>> Release note highlights can be found here:
>>>> https://cwiki.apache.org/confluence/display/NIFI/
>>> Release+Notes#ReleaseNotes-Version1.0.0
>>>>
>>>> The vote will be open for 72 hours.
>>>> Please download the release candidate and evaluate the necessary items
>>>> including checking hashes, signatures, build from source, and test.
>> Then
>>>> please vote:
>>>>
>>>> [ ] +1 Release this package as nifi-1.0.0
>>>> [ ] +0 no opinion
>>>> [ ] -1 Do not release this package because...
>>>>
>>>> Thanks!
>>>
>>
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Joe Skora <js...@gmail.com>.
Ok, I'm changing my vote to +1!
I don't know the root cause is, but I changed the "latch.await" timeouts
from 5 to 60 seconds and the test pass. :-D
This was the only system that built the 1.0.0-beta on the first try, the
only change since then is the Windows 10 Anniversary update last week. And
the firewall is off.
On Sun, Aug 28, 2016 at 10:13 PM, Joe Percivall <
joepercivall@yahoo.com.invalid> wrote:
> Ah sorry, misread your message. I see you ruled out an EOL issue.
>
> Any idea what would change in regards to the SMTP tests in Windows 8 vs 10
> (or your system vs mine)?
>
> Joe
> - - - - - -
> Joseph Percivall
> linkedin.com/in/Percivall
> e: joepercivall@yahoo.com
>
>
>
>
> On Sunday, August 28, 2016 10:10 PM, Joe Percivall <jo...@yahoo.com>
> wrote:
> JoeS,
>
> I tested the build on Windows 8 and everything worked fine for me.
> Wouldn't an EOL issue show up in all Windows builds?
>
> Joe
> - - - - - -
> Joseph Percivall
> linkedin.com/in/Percivall
> e: joepercivall@yahoo.com
>
>
>
>
>
> On Sunday, August 28, 2016 10:05 PM, Joe Skora <js...@gmail.com> wrote:
> -1 (non-binding)
>
> It looks good in general, but Windows 10 unit tests consistently fail in
> TestListenSMTP.
>
> It builds fine on OS X and Ubuntu has one error described below.
>
> It runs fine on OS X and Ubuntu including AWS S3 and HandleHTTP processors.
>
> 1. signature verifies
> 2. hashes verify
> 3. build and passes RAT check
> a. OS X - builds and runs ok
> b. Ubuntu 15.10 - builds with one error but runs ok [1]
> c. Windows 10 - *FAILS* unit tests:
> - Failing tests are
> TestListSMTP.validateSuccessfulInteraction
> TestListSMTP.validateSuccessfulInteractionWithTls
> TestListSMTP.validateTooLargeMessage
> - I tried Git core.autocrlf set to "input" and "false", in case it
> was an EOL issue, but that made no difference.
> 4. LICENSE, NOTICE, and README.MD look good
> 5. RC commit ID is good
> 6. RC is branched off correct commit ID
> 7. binary runs as expected with a test flow include AWS *S3 and HandleHTTP*
> processors
> (including FetchFile, FetchS3Object, GenerateFlowFile, GetFile,
> HandleHttpRequest, HandleHttpResponse, InvokeHttp, ListS3,
> LogAttribute, PutFile, RouteOnAttribute, TransformXML, and
> UpdateAttribute processors)
>
>
> [1] The build fails on Ubuntu 15.10 like it did with 1.0.0-BETA, I have to
> build with "--fail-never" to get a binary. The failing test is
> TestPutUDP.testInvalidIPAddress(), it could be a JVM bug or network issue
> on the box, but the system shows no other problems. Tracking through the
> call stack, the native method Inet6AddressImpl.lookupAllHostAddr() throws
> UnknownHostException on other systems with stacktraces similar to the one
> below, but on this one there is no exception thrown using Java 8 and Java 7
> only throws the exception if the "-Djava.net.preferIPv4Stack=true"
> property
> is defined. Since the Mock framework doesn't actually transfer these files
> to the bad IP the test expects the files to route to "failure" because fo
> the exception but without the exception they go to "success"and the test
> fails.
> java.net.UnknownHostException: 300.300.300.300: unknown error
> at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
> at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928)
> at
> java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323)
> at java.net.InetAddress.getAllByName0(InetAddress.java:1276)
> at java.net.InetAddress.getAllByName(InetAddress.java:1192)
> at java.net.InetAddress.getAllByName(InetAddress.java:1126)
> at java.net.InetAddress.getByName(InetAddress.java:1076)
> at TestBadIpAddress.main(TestBadIpAddress.java:13)
>
>
> On Sun, Aug 28, 2016 at 9:25 PM, Bryan Rosander <br...@gmail.com>
> wrote:
>
> > Downloaded source
> >
> > Verified checksums
> >
> > Ran build with contrib-check and empty local repo
> >
> > Ran build with –T2 concurrency and empty local repo
> >
> > Used tls-toolkit to generate 4 localhost keystore, truststore,
> > nifi.properties and a single client certificate
> >
> > Started all 4 instances verified no port conflicts, correct certificate
> > usage
> >
> > Imported CA certificate, client cert into browser, verified tls working
> > properly
> >
> > +1 (non-binding)
> >
> > Thanks,
> > Bryan
> >
> > On Aug 28, 2016 7:30 PM, "Tony Kurc" <tr...@gmail.com> wrote:
> >
> > > +1 (binding)
> > >
> > > Full build starting with empty maven repository on Ubuntu 14.04
> (x86_64)
> > > successfully.
> > >
> > > Verified signatures and hashes. Reviewed LICENSE/NOTICE.
> > >
> > > Ran a simple flow with no issues. Ran a few nifi-toolkit commands.
> > >
> > >
> > >
> > > On Sun, Aug 28, 2016 at 5:29 PM, Joe Witt <jo...@gmail.com> wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > Full clean build w/contrib check good.
> > > >
> > > > Verified signatures (and strength), hashes, and LICENSE/NOTICE within
> > > > sources and convenience binaries.
> > > >
> > > > Verified the commit the release was based on.
> > > >
> > > > Ran single and multi-node clusters with favorable results.
> > > >
> > > > For future release please do move any necessary elements of the UnRar
> > > > item to NOTICE where category B items belong. See here for LEGAL
> > > > discuss https://issues.apache.org/jira/browse/LEGAL-52 on this.
> > > >
> > > > Great job pulling the release together again JoeP.
> > > >
> > > > Thanks
> > > > Joe
> > > >
> > > > On Fri, Aug 26, 2016 at 12:25 PM, Joe Percivall
> > > > <jo...@yahoo.com.invalid> wrote:
> > > > > Hello Apache NiFi Community,
> > > > >
> > > > > I am pleased to be calling this vote for the source release of
> Apache
> > > > NiFi,
> > > > > nifi-1.0.0.
> > > > >
> > > > > The source zip, including signatures, digests, etc. can be found
> at:
> > > > > https://repository.apache.org/content/repositories/
> > orgapachenifi-1090/
> > > > >
> > > > > Note: There is a second binary being distributed now, the NiFi
> > Toolkit.
> > > > It
> > > > > can be used to facilitate securing a NiFi instance.
> > > > >
> > > > > The Git tag is nifi-1.0.0-RC1
> > > > > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > > > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > > > 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > > > * https://github.com/apache/nifi/commit/
> > 74d5224783dfdc513f6b3ad5ed9667
> > > > 1d3c581707
> > > > >
> > > > > Checksums of nifi-1.0.0-source-release.zip:
> > > > > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> > > > > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> > > > > SHA256: 22167ede5127683ca8de6dbd2fb911
> 2cb1de650b7cfff7e640c905521447
> > > af92
> > > > >
> > > > > Release artifacts are signed with the following key:
> > > > > https://people.apache.org/keys/committer/jpercivall
> > > > >
> > > > > KEYS file available here:
> > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > > >
> > > > > 595 issues were closed/resolved for this release:
> > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > projectId=12316020&version=12332640
> > > > >
> > > > > Release note highlights can be found here:
> > > > > https://cwiki.apache.org/confluence/display/NIFI/
> > > > Release+Notes#ReleaseNotes-Version1.0.0
> > > > >
> > > > > The vote will be open for 72 hours.
> > > > > Please download the release candidate and evaluate the necessary
> > items
> > > > > including checking hashes, signatures, build from source, and test.
> > > Then
> > > > > please vote:
> > > > >
> > > > > [ ] +1 Release this package as nifi-1.0.0
> > > > > [ ] +0 no opinion
> > > > > [ ] -1 Do not release this package because...
> > > > >
> > > > > Thanks!
> > > >
> > >
> >
>
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Joe Percivall <jo...@yahoo.com.INVALID>.
Ah sorry, misread your message. I see you ruled out an EOL issue.
Any idea what would change in regards to the SMTP tests in Windows 8 vs 10 (or your system vs mine)?
Joe
- - - - - -
Joseph Percivall
linkedin.com/in/Percivall
e: joepercivall@yahoo.com
On Sunday, August 28, 2016 10:10 PM, Joe Percivall <jo...@yahoo.com> wrote:
JoeS,
I tested the build on Windows 8 and everything worked fine for me. Wouldn't an EOL issue show up in all Windows builds?
Joe
- - - - - -
Joseph Percivall
linkedin.com/in/Percivall
e: joepercivall@yahoo.com
On Sunday, August 28, 2016 10:05 PM, Joe Skora <js...@gmail.com> wrote:
-1 (non-binding)
It looks good in general, but Windows 10 unit tests consistently fail in
TestListenSMTP.
It builds fine on OS X and Ubuntu has one error described below.
It runs fine on OS X and Ubuntu including AWS S3 and HandleHTTP processors.
1. signature verifies
2. hashes verify
3. build and passes RAT check
a. OS X - builds and runs ok
b. Ubuntu 15.10 - builds with one error but runs ok [1]
c. Windows 10 - *FAILS* unit tests:
- Failing tests are
TestListSMTP.validateSuccessfulInteraction
TestListSMTP.validateSuccessfulInteractionWithTls
TestListSMTP.validateTooLargeMessage
- I tried Git core.autocrlf set to "input" and "false", in case it
was an EOL issue, but that made no difference.
4. LICENSE, NOTICE, and README.MD look good
5. RC commit ID is good
6. RC is branched off correct commit ID
7. binary runs as expected with a test flow include AWS *S3 and HandleHTTP*
processors
(including FetchFile, FetchS3Object, GenerateFlowFile, GetFile,
HandleHttpRequest, HandleHttpResponse, InvokeHttp, ListS3,
LogAttribute, PutFile, RouteOnAttribute, TransformXML, and
UpdateAttribute processors)
[1] The build fails on Ubuntu 15.10 like it did with 1.0.0-BETA, I have to
build with "--fail-never" to get a binary. The failing test is
TestPutUDP.testInvalidIPAddress(), it could be a JVM bug or network issue
on the box, but the system shows no other problems. Tracking through the
call stack, the native method Inet6AddressImpl.lookupAllHostAddr() throws
UnknownHostException on other systems with stacktraces similar to the one
below, but on this one there is no exception thrown using Java 8 and Java 7
only throws the exception if the "-Djava.net.preferIPv4Stack=true" property
is defined. Since the Mock framework doesn't actually transfer these files
to the bad IP the test expects the files to route to "failure" because fo
the exception but without the exception they go to "success"and the test
fails.
java.net.UnknownHostException: 300.300.300.300: unknown error
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928)
at
java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323)
at java.net.InetAddress.getAllByName0(InetAddress.java:1276)
at java.net.InetAddress.getAllByName(InetAddress.java:1192)
at java.net.InetAddress.getAllByName(InetAddress.java:1126)
at java.net.InetAddress.getByName(InetAddress.java:1076)
at TestBadIpAddress.main(TestBadIpAddress.java:13)
On Sun, Aug 28, 2016 at 9:25 PM, Bryan Rosander <br...@gmail.com>
wrote:
> Downloaded source
>
> Verified checksums
>
> Ran build with contrib-check and empty local repo
>
> Ran build with –T2 concurrency and empty local repo
>
> Used tls-toolkit to generate 4 localhost keystore, truststore,
> nifi.properties and a single client certificate
>
> Started all 4 instances verified no port conflicts, correct certificate
> usage
>
> Imported CA certificate, client cert into browser, verified tls working
> properly
>
> +1 (non-binding)
>
> Thanks,
> Bryan
>
> On Aug 28, 2016 7:30 PM, "Tony Kurc" <tr...@gmail.com> wrote:
>
> > +1 (binding)
> >
> > Full build starting with empty maven repository on Ubuntu 14.04 (x86_64)
> > successfully.
> >
> > Verified signatures and hashes. Reviewed LICENSE/NOTICE.
> >
> > Ran a simple flow with no issues. Ran a few nifi-toolkit commands.
> >
> >
> >
> > On Sun, Aug 28, 2016 at 5:29 PM, Joe Witt <jo...@gmail.com> wrote:
> >
> > > +1 (binding)
> > >
> > > Full clean build w/contrib check good.
> > >
> > > Verified signatures (and strength), hashes, and LICENSE/NOTICE within
> > > sources and convenience binaries.
> > >
> > > Verified the commit the release was based on.
> > >
> > > Ran single and multi-node clusters with favorable results.
> > >
> > > For future release please do move any necessary elements of the UnRar
> > > item to NOTICE where category B items belong. See here for LEGAL
> > > discuss https://issues.apache.org/jira/browse/LEGAL-52 on this.
> > >
> > > Great job pulling the release together again JoeP.
> > >
> > > Thanks
> > > Joe
> > >
> > > On Fri, Aug 26, 2016 at 12:25 PM, Joe Percivall
> > > <jo...@yahoo.com.invalid> wrote:
> > > > Hello Apache NiFi Community,
> > > >
> > > > I am pleased to be calling this vote for the source release of Apache
> > > NiFi,
> > > > nifi-1.0.0.
> > > >
> > > > The source zip, including signatures, digests, etc. can be found at:
> > > > https://repository.apache.org/content/repositories/
> orgapachenifi-1090/
> > > >
> > > > Note: There is a second binary being distributed now, the NiFi
> Toolkit.
> > > It
> > > > can be used to facilitate securing a NiFi instance.
> > > >
> > > > The Git tag is nifi-1.0.0-RC1
> > > > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > > 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > > * https://github.com/apache/nifi/commit/
> 74d5224783dfdc513f6b3ad5ed9667
> > > 1d3c581707
> > > >
> > > > Checksums of nifi-1.0.0-source-release.zip:
> > > > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> > > > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> > > > SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447
> > af92
> > > >
> > > > Release artifacts are signed with the following key:
> > > > https://people.apache.org/keys/committer/jpercivall
> > > >
> > > > KEYS file available here:
> > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > >
> > > > 595 issues were closed/resolved for this release:
> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > projectId=12316020&version=12332640
> > > >
> > > > Release note highlights can be found here:
> > > > https://cwiki.apache.org/confluence/display/NIFI/
> > > Release+Notes#ReleaseNotes-Version1.0.0
> > > >
> > > > The vote will be open for 72 hours.
> > > > Please download the release candidate and evaluate the necessary
> items
> > > > including checking hashes, signatures, build from source, and test.
> > Then
> > > > please vote:
> > > >
> > > > [ ] +1 Release this package as nifi-1.0.0
> > > > [ ] +0 no opinion
> > > > [ ] -1 Do not release this package because...
> > > >
> > > > Thanks!
> > >
> >
>
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Joe Percivall <jo...@yahoo.com.INVALID>.
JoeS,
I tested the build on Windows 8 and everything worked fine for me. Wouldn't an EOL issue show up in all Windows builds?
Joe
- - - - - -
Joseph Percivall
linkedin.com/in/Percivall
e: joepercivall@yahoo.com
On Sunday, August 28, 2016 10:05 PM, Joe Skora <js...@gmail.com> wrote:
-1 (non-binding)
It looks good in general, but Windows 10 unit tests consistently fail in
TestListenSMTP.
It builds fine on OS X and Ubuntu has one error described below.
It runs fine on OS X and Ubuntu including AWS S3 and HandleHTTP processors.
1. signature verifies
2. hashes verify
3. build and passes RAT check
a. OS X - builds and runs ok
b. Ubuntu 15.10 - builds with one error but runs ok [1]
c. Windows 10 - *FAILS* unit tests:
- Failing tests are
TestListSMTP.validateSuccessfulInteraction
TestListSMTP.validateSuccessfulInteractionWithTls
TestListSMTP.validateTooLargeMessage
- I tried Git core.autocrlf set to "input" and "false", in case it
was an EOL issue, but that made no difference.
4. LICENSE, NOTICE, and README.MD look good
5. RC commit ID is good
6. RC is branched off correct commit ID
7. binary runs as expected with a test flow include AWS *S3 and HandleHTTP*
processors
(including FetchFile, FetchS3Object, GenerateFlowFile, GetFile,
HandleHttpRequest, HandleHttpResponse, InvokeHttp, ListS3,
LogAttribute, PutFile, RouteOnAttribute, TransformXML, and
UpdateAttribute processors)
[1] The build fails on Ubuntu 15.10 like it did with 1.0.0-BETA, I have to
build with "--fail-never" to get a binary. The failing test is
TestPutUDP.testInvalidIPAddress(), it could be a JVM bug or network issue
on the box, but the system shows no other problems. Tracking through the
call stack, the native method Inet6AddressImpl.lookupAllHostAddr() throws
UnknownHostException on other systems with stacktraces similar to the one
below, but on this one there is no exception thrown using Java 8 and Java 7
only throws the exception if the "-Djava.net.preferIPv4Stack=true" property
is defined. Since the Mock framework doesn't actually transfer these files
to the bad IP the test expects the files to route to "failure" because fo
the exception but without the exception they go to "success"and the test
fails.
java.net.UnknownHostException: 300.300.300.300: unknown error
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928)
at
java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323)
at java.net.InetAddress.getAllByName0(InetAddress.java:1276)
at java.net.InetAddress.getAllByName(InetAddress.java:1192)
at java.net.InetAddress.getAllByName(InetAddress.java:1126)
at java.net.InetAddress.getByName(InetAddress.java:1076)
at TestBadIpAddress.main(TestBadIpAddress.java:13)
On Sun, Aug 28, 2016 at 9:25 PM, Bryan Rosander <br...@gmail.com>
wrote:
> Downloaded source
>
> Verified checksums
>
> Ran build with contrib-check and empty local repo
>
> Ran build with –T2 concurrency and empty local repo
>
> Used tls-toolkit to generate 4 localhost keystore, truststore,
> nifi.properties and a single client certificate
>
> Started all 4 instances verified no port conflicts, correct certificate
> usage
>
> Imported CA certificate, client cert into browser, verified tls working
> properly
>
> +1 (non-binding)
>
> Thanks,
> Bryan
>
> On Aug 28, 2016 7:30 PM, "Tony Kurc" <tr...@gmail.com> wrote:
>
> > +1 (binding)
> >
> > Full build starting with empty maven repository on Ubuntu 14.04 (x86_64)
> > successfully.
> >
> > Verified signatures and hashes. Reviewed LICENSE/NOTICE.
> >
> > Ran a simple flow with no issues. Ran a few nifi-toolkit commands.
> >
> >
> >
> > On Sun, Aug 28, 2016 at 5:29 PM, Joe Witt <jo...@gmail.com> wrote:
> >
> > > +1 (binding)
> > >
> > > Full clean build w/contrib check good.
> > >
> > > Verified signatures (and strength), hashes, and LICENSE/NOTICE within
> > > sources and convenience binaries.
> > >
> > > Verified the commit the release was based on.
> > >
> > > Ran single and multi-node clusters with favorable results.
> > >
> > > For future release please do move any necessary elements of the UnRar
> > > item to NOTICE where category B items belong. See here for LEGAL
> > > discuss https://issues.apache.org/jira/browse/LEGAL-52 on this.
> > >
> > > Great job pulling the release together again JoeP.
> > >
> > > Thanks
> > > Joe
> > >
> > > On Fri, Aug 26, 2016 at 12:25 PM, Joe Percivall
> > > <jo...@yahoo.com.invalid> wrote:
> > > > Hello Apache NiFi Community,
> > > >
> > > > I am pleased to be calling this vote for the source release of Apache
> > > NiFi,
> > > > nifi-1.0.0.
> > > >
> > > > The source zip, including signatures, digests, etc. can be found at:
> > > > https://repository.apache.org/content/repositories/
> orgapachenifi-1090/
> > > >
> > > > Note: There is a second binary being distributed now, the NiFi
> Toolkit.
> > > It
> > > > can be used to facilitate securing a NiFi instance.
> > > >
> > > > The Git tag is nifi-1.0.0-RC1
> > > > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > > 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > > * https://github.com/apache/nifi/commit/
> 74d5224783dfdc513f6b3ad5ed9667
> > > 1d3c581707
> > > >
> > > > Checksums of nifi-1.0.0-source-release.zip:
> > > > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> > > > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> > > > SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447
> > af92
> > > >
> > > > Release artifacts are signed with the following key:
> > > > https://people.apache.org/keys/committer/jpercivall
> > > >
> > > > KEYS file available here:
> > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > >
> > > > 595 issues were closed/resolved for this release:
> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > projectId=12316020&version=12332640
> > > >
> > > > Release note highlights can be found here:
> > > > https://cwiki.apache.org/confluence/display/NIFI/
> > > Release+Notes#ReleaseNotes-Version1.0.0
> > > >
> > > > The vote will be open for 72 hours.
> > > > Please download the release candidate and evaluate the necessary
> items
> > > > including checking hashes, signatures, build from source, and test.
> > Then
> > > > please vote:
> > > >
> > > > [ ] +1 Release this package as nifi-1.0.0
> > > > [ ] +0 no opinion
> > > > [ ] -1 Do not release this package because...
> > > >
> > > > Thanks!
> > >
> >
>
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Aldrin Piri <al...@gmail.com>.
I have also been running through some verification and can confirm the same
test failures in a similar Windows 10 environment. Indeed, increasing the
timeout remedied those issues. My times were not as long as Joe Skora's,
but in excess of the configured timeout.
On Sun, Aug 28, 2016 at 11:46 PM, Joe Skora <js...@gmail.com> wrote:
> So, for the record, here are the test times.
> TestListenSMTP.validateSuccessfulInteraction - 59s 74ms
> TestListenSMTP.validateSuccessfulInteractionWithTls - 56s 111ms
> TestListenSMTP.validateTooLargeMessage - 19s 123ms
>
> This system runs Windows 10 Pro, Version 1607, OS Build 14393.82 on an
> Intel Core i7-4720HQ @2.60 GHz with 16 GB of RAM. I've tried it with the
> Windows Defender firewall disabled and enabled with rules permitting Java
> to make and receive connections.
>
>
> On Sun, Aug 28, 2016 at 10:50 PM, Joe Skora <js...@gmail.com> wrote:
>
> > Change that to +1 (non-binding)
> >
> > With longer timeouts the TestListenSMTP tests are now passing.
> >
> > On Sun, Aug 28, 2016 at 10:04 PM, Joe Skora <js...@gmail.com> wrote:
> >
> >> -1 (non-binding)
> >>
> >> It looks good in general, but Windows 10 unit tests consistently fail in
> >> TestListenSMTP.
> >>
> >> It builds fine on OS X and Ubuntu has one error described below.
> >>
> >> It runs fine on OS X and Ubuntu including AWS S3 and HandleHTTP
> >> processors.
> >>
> >> 1. signature verifies
> >> 2. hashes verify
> >> 3. build and passes RAT check
> >> a. OS X - builds and runs ok
> >> b. Ubuntu 15.10 - builds with one error but runs ok [1]
> >> c. Windows 10 - *FAILS* unit tests:
> >> - Failing tests are
> >> TestListSMTP.validateSuccessfulInteraction
> >> TestListSMTP.validateSuccessfulInteractionWithTls
> >> TestListSMTP.validateTooLargeMessage
> >> - I tried Git core.autocrlf set to "input" and "false", in case
> it
> >> was an EOL issue, but that made no difference.
> >> 4. LICENSE, NOTICE, and README.MD look good
> >> 5. RC commit ID is good
> >> 6. RC is branched off correct commit ID
> >> 7. binary runs as expected with a test flow include AWS *S3 and
> >> HandleHTTP* processors
> >> (including FetchFile, FetchS3Object, GenerateFlowFile, GetFile,
> >> HandleHttpRequest, HandleHttpResponse, InvokeHttp, ListS3,
> >> LogAttribute, PutFile, RouteOnAttribute, TransformXML, and
> >> UpdateAttribute processors)
> >>
> >>
> >> [1] The build fails on Ubuntu 15.10 like it did with 1.0.0-BETA, I have
> >> to build with "--fail-never" to get a binary. The failing test is
> >> TestPutUDP.testInvalidIPAddress(), it could be a JVM bug or network
> >> issue on the box, but the system shows no other problems. Tracking
> through
> >> the call stack, the native method Inet6AddressImpl.lookupAllHostAddr()
> >> throws UnknownHostException on other systems with stacktraces similar to
> >> the one below, but on this one there is no exception thrown using Java 8
> >> and Java 7 only throws the exception if the "-Djava.net.preferIPv4Stack=
> true"
> >> property is defined. Since the Mock framework doesn't actually transfer
> >> these files to the bad IP the test expects the files to route to
> "failure"
> >> because fo the exception but without the exception they go to
> "success"and
> >> the test fails.
> >> java.net.UnknownHostException: 300.300.300.300: unknown error
> >> at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
> >> at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.
> java:928)
> >> at java.net.InetAddress.getAddressesFromNameService(InetAddress
> >> .java:1323)
> >> at java.net.InetAddress.getAllByName0(InetAddress.java:1276)
> >> at java.net.InetAddress.getAllByName(InetAddress.java:1192)
> >> at java.net.InetAddress.getAllByName(InetAddress.java:1126)
> >> at java.net.InetAddress.getByName(InetAddress.java:1076)
> >> at TestBadIpAddress.main(TestBadIpAddress.java:13)
> >>
> >> On Sun, Aug 28, 2016 at 9:25 PM, Bryan Rosander <
> bryanrosander@gmail.com>
> >> wrote:
> >>
> >>> Downloaded source
> >>>
> >>> Verified checksums
> >>>
> >>> Ran build with contrib-check and empty local repo
> >>>
> >>> Ran build with –T2 concurrency and empty local repo
> >>>
> >>> Used tls-toolkit to generate 4 localhost keystore, truststore,
> >>> nifi.properties and a single client certificate
> >>>
> >>> Started all 4 instances verified no port conflicts, correct certificate
> >>> usage
> >>>
> >>> Imported CA certificate, client cert into browser, verified tls working
> >>> properly
> >>>
> >>> +1 (non-binding)
> >>>
> >>> Thanks,
> >>> Bryan
> >>>
> >>> On Aug 28, 2016 7:30 PM, "Tony Kurc" <tr...@gmail.com> wrote:
> >>>
> >>> > +1 (binding)
> >>> >
> >>> > Full build starting with empty maven repository on Ubuntu 14.04
> >>> (x86_64)
> >>> > successfully.
> >>> >
> >>> > Verified signatures and hashes. Reviewed LICENSE/NOTICE.
> >>> >
> >>> > Ran a simple flow with no issues. Ran a few nifi-toolkit commands.
> >>> >
> >>> >
> >>> >
> >>> > On Sun, Aug 28, 2016 at 5:29 PM, Joe Witt <jo...@gmail.com>
> wrote:
> >>> >
> >>> > > +1 (binding)
> >>> > >
> >>> > > Full clean build w/contrib check good.
> >>> > >
> >>> > > Verified signatures (and strength), hashes, and LICENSE/NOTICE
> within
> >>> > > sources and convenience binaries.
> >>> > >
> >>> > > Verified the commit the release was based on.
> >>> > >
> >>> > > Ran single and multi-node clusters with favorable results.
> >>> > >
> >>> > > For future release please do move any necessary elements of the
> UnRar
> >>> > > item to NOTICE where category B items belong. See here for LEGAL
> >>> > > discuss https://issues.apache.org/jira/browse/LEGAL-52 on this.
> >>> > >
> >>> > > Great job pulling the release together again JoeP.
> >>> > >
> >>> > > Thanks
> >>> > > Joe
> >>> > >
> >>> > > On Fri, Aug 26, 2016 at 12:25 PM, Joe Percivall
> >>> > > <jo...@yahoo.com.invalid> wrote:
> >>> > > > Hello Apache NiFi Community,
> >>> > > >
> >>> > > > I am pleased to be calling this vote for the source release of
> >>> Apache
> >>> > > NiFi,
> >>> > > > nifi-1.0.0.
> >>> > > >
> >>> > > > The source zip, including signatures, digests, etc. can be found
> >>> at:
> >>> > > > https://repository.apache.org/content/repositories/orgapache
> >>> nifi-1090/
> >>> > > >
> >>> > > > Note: There is a second binary being distributed now, the NiFi
> >>> Toolkit.
> >>> > > It
> >>> > > > can be used to facilitate securing a NiFi instance.
> >>> > > >
> >>> > > > The Git tag is nifi-1.0.0-RC1
> >>> > > > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> >>> > > > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> >>> > > 74d5224783dfdc513f6b3ad5ed96671d3c581707
> >>> > > > * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3a
> >>> d5ed9667
> >>> > > 1d3c581707
> >>> > > >
> >>> > > > Checksums of nifi-1.0.0-source-release.zip:
> >>> > > > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> >>> > > > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> >>> > > > SHA256: 22167ede5127683ca8de6dbd2fb911
> >>> 2cb1de650b7cfff7e640c905521447
> >>> > af92
> >>> > > >
> >>> > > > Release artifacts are signed with the following key:
> >>> > > > https://people.apache.org/keys/committer/jpercivall
> >>> > > >
> >>> > > > KEYS file available here:
> >>> > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >>> > > >
> >>> > > > 595 issues were closed/resolved for this release:
> >>> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >>> > > projectId=12316020&version=12332640
> >>> > > >
> >>> > > > Release note highlights can be found here:
> >>> > > > https://cwiki.apache.org/confluence/display/NIFI/
> >>> > > Release+Notes#ReleaseNotes-Version1.0.0
> >>> > > >
> >>> > > > The vote will be open for 72 hours.
> >>> > > > Please download the release candidate and evaluate the necessary
> >>> items
> >>> > > > including checking hashes, signatures, build from source, and
> test.
> >>> > Then
> >>> > > > please vote:
> >>> > > >
> >>> > > > [ ] +1 Release this package as nifi-1.0.0
> >>> > > > [ ] +0 no opinion
> >>> > > > [ ] -1 Do not release this package because...
> >>> > > >
> >>> > > > Thanks!
> >>> > >
> >>> >
> >>>
> >>
> >>
> >
>
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Joe Skora <js...@gmail.com>.
So, for the record, here are the test times.
TestListenSMTP.validateSuccessfulInteraction - 59s 74ms
TestListenSMTP.validateSuccessfulInteractionWithTls - 56s 111ms
TestListenSMTP.validateTooLargeMessage - 19s 123ms
This system runs Windows 10 Pro, Version 1607, OS Build 14393.82 on an
Intel Core i7-4720HQ @2.60 GHz with 16 GB of RAM. I've tried it with the
Windows Defender firewall disabled and enabled with rules permitting Java
to make and receive connections.
On Sun, Aug 28, 2016 at 10:50 PM, Joe Skora <js...@gmail.com> wrote:
> Change that to +1 (non-binding)
>
> With longer timeouts the TestListenSMTP tests are now passing.
>
> On Sun, Aug 28, 2016 at 10:04 PM, Joe Skora <js...@gmail.com> wrote:
>
>> -1 (non-binding)
>>
>> It looks good in general, but Windows 10 unit tests consistently fail in
>> TestListenSMTP.
>>
>> It builds fine on OS X and Ubuntu has one error described below.
>>
>> It runs fine on OS X and Ubuntu including AWS S3 and HandleHTTP
>> processors.
>>
>> 1. signature verifies
>> 2. hashes verify
>> 3. build and passes RAT check
>> a. OS X - builds and runs ok
>> b. Ubuntu 15.10 - builds with one error but runs ok [1]
>> c. Windows 10 - *FAILS* unit tests:
>> - Failing tests are
>> TestListSMTP.validateSuccessfulInteraction
>> TestListSMTP.validateSuccessfulInteractionWithTls
>> TestListSMTP.validateTooLargeMessage
>> - I tried Git core.autocrlf set to "input" and "false", in case it
>> was an EOL issue, but that made no difference.
>> 4. LICENSE, NOTICE, and README.MD look good
>> 5. RC commit ID is good
>> 6. RC is branched off correct commit ID
>> 7. binary runs as expected with a test flow include AWS *S3 and
>> HandleHTTP* processors
>> (including FetchFile, FetchS3Object, GenerateFlowFile, GetFile,
>> HandleHttpRequest, HandleHttpResponse, InvokeHttp, ListS3,
>> LogAttribute, PutFile, RouteOnAttribute, TransformXML, and
>> UpdateAttribute processors)
>>
>>
>> [1] The build fails on Ubuntu 15.10 like it did with 1.0.0-BETA, I have
>> to build with "--fail-never" to get a binary. The failing test is
>> TestPutUDP.testInvalidIPAddress(), it could be a JVM bug or network
>> issue on the box, but the system shows no other problems. Tracking through
>> the call stack, the native method Inet6AddressImpl.lookupAllHostAddr()
>> throws UnknownHostException on other systems with stacktraces similar to
>> the one below, but on this one there is no exception thrown using Java 8
>> and Java 7 only throws the exception if the "-Djava.net.preferIPv4Stack=true"
>> property is defined. Since the Mock framework doesn't actually transfer
>> these files to the bad IP the test expects the files to route to "failure"
>> because fo the exception but without the exception they go to "success"and
>> the test fails.
>> java.net.UnknownHostException: 300.300.300.300: unknown error
>> at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
>> at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928)
>> at java.net.InetAddress.getAddressesFromNameService(InetAddress
>> .java:1323)
>> at java.net.InetAddress.getAllByName0(InetAddress.java:1276)
>> at java.net.InetAddress.getAllByName(InetAddress.java:1192)
>> at java.net.InetAddress.getAllByName(InetAddress.java:1126)
>> at java.net.InetAddress.getByName(InetAddress.java:1076)
>> at TestBadIpAddress.main(TestBadIpAddress.java:13)
>>
>> On Sun, Aug 28, 2016 at 9:25 PM, Bryan Rosander <br...@gmail.com>
>> wrote:
>>
>>> Downloaded source
>>>
>>> Verified checksums
>>>
>>> Ran build with contrib-check and empty local repo
>>>
>>> Ran build with –T2 concurrency and empty local repo
>>>
>>> Used tls-toolkit to generate 4 localhost keystore, truststore,
>>> nifi.properties and a single client certificate
>>>
>>> Started all 4 instances verified no port conflicts, correct certificate
>>> usage
>>>
>>> Imported CA certificate, client cert into browser, verified tls working
>>> properly
>>>
>>> +1 (non-binding)
>>>
>>> Thanks,
>>> Bryan
>>>
>>> On Aug 28, 2016 7:30 PM, "Tony Kurc" <tr...@gmail.com> wrote:
>>>
>>> > +1 (binding)
>>> >
>>> > Full build starting with empty maven repository on Ubuntu 14.04
>>> (x86_64)
>>> > successfully.
>>> >
>>> > Verified signatures and hashes. Reviewed LICENSE/NOTICE.
>>> >
>>> > Ran a simple flow with no issues. Ran a few nifi-toolkit commands.
>>> >
>>> >
>>> >
>>> > On Sun, Aug 28, 2016 at 5:29 PM, Joe Witt <jo...@gmail.com> wrote:
>>> >
>>> > > +1 (binding)
>>> > >
>>> > > Full clean build w/contrib check good.
>>> > >
>>> > > Verified signatures (and strength), hashes, and LICENSE/NOTICE within
>>> > > sources and convenience binaries.
>>> > >
>>> > > Verified the commit the release was based on.
>>> > >
>>> > > Ran single and multi-node clusters with favorable results.
>>> > >
>>> > > For future release please do move any necessary elements of the UnRar
>>> > > item to NOTICE where category B items belong. See here for LEGAL
>>> > > discuss https://issues.apache.org/jira/browse/LEGAL-52 on this.
>>> > >
>>> > > Great job pulling the release together again JoeP.
>>> > >
>>> > > Thanks
>>> > > Joe
>>> > >
>>> > > On Fri, Aug 26, 2016 at 12:25 PM, Joe Percivall
>>> > > <jo...@yahoo.com.invalid> wrote:
>>> > > > Hello Apache NiFi Community,
>>> > > >
>>> > > > I am pleased to be calling this vote for the source release of
>>> Apache
>>> > > NiFi,
>>> > > > nifi-1.0.0.
>>> > > >
>>> > > > The source zip, including signatures, digests, etc. can be found
>>> at:
>>> > > > https://repository.apache.org/content/repositories/orgapache
>>> nifi-1090/
>>> > > >
>>> > > > Note: There is a second binary being distributed now, the NiFi
>>> Toolkit.
>>> > > It
>>> > > > can be used to facilitate securing a NiFi instance.
>>> > > >
>>> > > > The Git tag is nifi-1.0.0-RC1
>>> > > > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
>>> > > > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
>>> > > 74d5224783dfdc513f6b3ad5ed96671d3c581707
>>> > > > * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3a
>>> d5ed9667
>>> > > 1d3c581707
>>> > > >
>>> > > > Checksums of nifi-1.0.0-source-release.zip:
>>> > > > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
>>> > > > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
>>> > > > SHA256: 22167ede5127683ca8de6dbd2fb911
>>> 2cb1de650b7cfff7e640c905521447
>>> > af92
>>> > > >
>>> > > > Release artifacts are signed with the following key:
>>> > > > https://people.apache.org/keys/committer/jpercivall
>>> > > >
>>> > > > KEYS file available here:
>>> > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
>>> > > >
>>> > > > 595 issues were closed/resolved for this release:
>>> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>>> > > projectId=12316020&version=12332640
>>> > > >
>>> > > > Release note highlights can be found here:
>>> > > > https://cwiki.apache.org/confluence/display/NIFI/
>>> > > Release+Notes#ReleaseNotes-Version1.0.0
>>> > > >
>>> > > > The vote will be open for 72 hours.
>>> > > > Please download the release candidate and evaluate the necessary
>>> items
>>> > > > including checking hashes, signatures, build from source, and test.
>>> > Then
>>> > > > please vote:
>>> > > >
>>> > > > [ ] +1 Release this package as nifi-1.0.0
>>> > > > [ ] +0 no opinion
>>> > > > [ ] -1 Do not release this package because...
>>> > > >
>>> > > > Thanks!
>>> > >
>>> >
>>>
>>
>>
>
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Joe Skora <js...@gmail.com>.
Change that to +1 (non-binding)
With longer timeouts the TestListenSMTP tests are now passing.
On Sun, Aug 28, 2016 at 10:04 PM, Joe Skora <js...@gmail.com> wrote:
> -1 (non-binding)
>
> It looks good in general, but Windows 10 unit tests consistently fail in
> TestListenSMTP.
>
> It builds fine on OS X and Ubuntu has one error described below.
>
> It runs fine on OS X and Ubuntu including AWS S3 and HandleHTTP processors.
>
> 1. signature verifies
> 2. hashes verify
> 3. build and passes RAT check
> a. OS X - builds and runs ok
> b. Ubuntu 15.10 - builds with one error but runs ok [1]
> c. Windows 10 - *FAILS* unit tests:
> - Failing tests are
> TestListSMTP.validateSuccessfulInteraction
> TestListSMTP.validateSuccessfulInteractionWithTls
> TestListSMTP.validateTooLargeMessage
> - I tried Git core.autocrlf set to "input" and "false", in case it
> was an EOL issue, but that made no difference.
> 4. LICENSE, NOTICE, and README.MD look good
> 5. RC commit ID is good
> 6. RC is branched off correct commit ID
> 7. binary runs as expected with a test flow include AWS *S3 and
> HandleHTTP* processors
> (including FetchFile, FetchS3Object, GenerateFlowFile, GetFile,
> HandleHttpRequest, HandleHttpResponse, InvokeHttp, ListS3,
> LogAttribute, PutFile, RouteOnAttribute, TransformXML, and
> UpdateAttribute processors)
>
>
> [1] The build fails on Ubuntu 15.10 like it did with 1.0.0-BETA, I have to
> build with "--fail-never" to get a binary. The failing test is TestPutUDP.testInvalidIPAddress(),
> it could be a JVM bug or network issue on the box, but the system shows no
> other problems. Tracking through the call stack, the native method
> Inet6AddressImpl.lookupAllHostAddr() throws UnknownHostException on other
> systems with stacktraces similar to the one below, but on this one there is
> no exception thrown using Java 8 and Java 7 only throws the exception if
> the "-Djava.net.preferIPv4Stack=true" property is defined. Since the
> Mock framework doesn't actually transfer these files to the bad IP the test
> expects the files to route to "failure" because fo the exception but
> without the exception they go to "success"and the test fails.
> java.net.UnknownHostException: 300.300.300.300: unknown error
> at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
> at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928)
> at java.net.InetAddress.getAddressesFromNameService(
> InetAddress.java:1323)
> at java.net.InetAddress.getAllByName0(InetAddress.java:1276)
> at java.net.InetAddress.getAllByName(InetAddress.java:1192)
> at java.net.InetAddress.getAllByName(InetAddress.java:1126)
> at java.net.InetAddress.getByName(InetAddress.java:1076)
> at TestBadIpAddress.main(TestBadIpAddress.java:13)
>
> On Sun, Aug 28, 2016 at 9:25 PM, Bryan Rosander <br...@gmail.com>
> wrote:
>
>> Downloaded source
>>
>> Verified checksums
>>
>> Ran build with contrib-check and empty local repo
>>
>> Ran build with –T2 concurrency and empty local repo
>>
>> Used tls-toolkit to generate 4 localhost keystore, truststore,
>> nifi.properties and a single client certificate
>>
>> Started all 4 instances verified no port conflicts, correct certificate
>> usage
>>
>> Imported CA certificate, client cert into browser, verified tls working
>> properly
>>
>> +1 (non-binding)
>>
>> Thanks,
>> Bryan
>>
>> On Aug 28, 2016 7:30 PM, "Tony Kurc" <tr...@gmail.com> wrote:
>>
>> > +1 (binding)
>> >
>> > Full build starting with empty maven repository on Ubuntu 14.04 (x86_64)
>> > successfully.
>> >
>> > Verified signatures and hashes. Reviewed LICENSE/NOTICE.
>> >
>> > Ran a simple flow with no issues. Ran a few nifi-toolkit commands.
>> >
>> >
>> >
>> > On Sun, Aug 28, 2016 at 5:29 PM, Joe Witt <jo...@gmail.com> wrote:
>> >
>> > > +1 (binding)
>> > >
>> > > Full clean build w/contrib check good.
>> > >
>> > > Verified signatures (and strength), hashes, and LICENSE/NOTICE within
>> > > sources and convenience binaries.
>> > >
>> > > Verified the commit the release was based on.
>> > >
>> > > Ran single and multi-node clusters with favorable results.
>> > >
>> > > For future release please do move any necessary elements of the UnRar
>> > > item to NOTICE where category B items belong. See here for LEGAL
>> > > discuss https://issues.apache.org/jira/browse/LEGAL-52 on this.
>> > >
>> > > Great job pulling the release together again JoeP.
>> > >
>> > > Thanks
>> > > Joe
>> > >
>> > > On Fri, Aug 26, 2016 at 12:25 PM, Joe Percivall
>> > > <jo...@yahoo.com.invalid> wrote:
>> > > > Hello Apache NiFi Community,
>> > > >
>> > > > I am pleased to be calling this vote for the source release of
>> Apache
>> > > NiFi,
>> > > > nifi-1.0.0.
>> > > >
>> > > > The source zip, including signatures, digests, etc. can be found at:
>> > > > https://repository.apache.org/content/repositories/orgapache
>> nifi-1090/
>> > > >
>> > > > Note: There is a second binary being distributed now, the NiFi
>> Toolkit.
>> > > It
>> > > > can be used to facilitate securing a NiFi instance.
>> > > >
>> > > > The Git tag is nifi-1.0.0-RC1
>> > > > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
>> > > > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
>> > > 74d5224783dfdc513f6b3ad5ed96671d3c581707
>> > > > * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3a
>> d5ed9667
>> > > 1d3c581707
>> > > >
>> > > > Checksums of nifi-1.0.0-source-release.zip:
>> > > > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
>> > > > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
>> > > > SHA256: 22167ede5127683ca8de6dbd2fb911
>> 2cb1de650b7cfff7e640c905521447
>> > af92
>> > > >
>> > > > Release artifacts are signed with the following key:
>> > > > https://people.apache.org/keys/committer/jpercivall
>> > > >
>> > > > KEYS file available here:
>> > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
>> > > >
>> > > > 595 issues were closed/resolved for this release:
>> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> > > projectId=12316020&version=12332640
>> > > >
>> > > > Release note highlights can be found here:
>> > > > https://cwiki.apache.org/confluence/display/NIFI/
>> > > Release+Notes#ReleaseNotes-Version1.0.0
>> > > >
>> > > > The vote will be open for 72 hours.
>> > > > Please download the release candidate and evaluate the necessary
>> items
>> > > > including checking hashes, signatures, build from source, and test.
>> > Then
>> > > > please vote:
>> > > >
>> > > > [ ] +1 Release this package as nifi-1.0.0
>> > > > [ ] +0 no opinion
>> > > > [ ] -1 Do not release this package because...
>> > > >
>> > > > Thanks!
>> > >
>> >
>>
>
>
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Joe Skora <js...@gmail.com>.
-1 (non-binding)
It looks good in general, but Windows 10 unit tests consistently fail in
TestListenSMTP.
It builds fine on OS X and Ubuntu has one error described below.
It runs fine on OS X and Ubuntu including AWS S3 and HandleHTTP processors.
1. signature verifies
2. hashes verify
3. build and passes RAT check
a. OS X - builds and runs ok
b. Ubuntu 15.10 - builds with one error but runs ok [1]
c. Windows 10 - *FAILS* unit tests:
- Failing tests are
TestListSMTP.validateSuccessfulInteraction
TestListSMTP.validateSuccessfulInteractionWithTls
TestListSMTP.validateTooLargeMessage
- I tried Git core.autocrlf set to "input" and "false", in case it
was an EOL issue, but that made no difference.
4. LICENSE, NOTICE, and README.MD look good
5. RC commit ID is good
6. RC is branched off correct commit ID
7. binary runs as expected with a test flow include AWS *S3 and HandleHTTP*
processors
(including FetchFile, FetchS3Object, GenerateFlowFile, GetFile,
HandleHttpRequest, HandleHttpResponse, InvokeHttp, ListS3,
LogAttribute, PutFile, RouteOnAttribute, TransformXML, and
UpdateAttribute processors)
[1] The build fails on Ubuntu 15.10 like it did with 1.0.0-BETA, I have to
build with "--fail-never" to get a binary. The failing test is
TestPutUDP.testInvalidIPAddress(), it could be a JVM bug or network issue
on the box, but the system shows no other problems. Tracking through the
call stack, the native method Inet6AddressImpl.lookupAllHostAddr() throws
UnknownHostException on other systems with stacktraces similar to the one
below, but on this one there is no exception thrown using Java 8 and Java 7
only throws the exception if the "-Djava.net.preferIPv4Stack=true" property
is defined. Since the Mock framework doesn't actually transfer these files
to the bad IP the test expects the files to route to "failure" because fo
the exception but without the exception they go to "success"and the test
fails.
java.net.UnknownHostException: 300.300.300.300: unknown error
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928)
at
java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323)
at java.net.InetAddress.getAllByName0(InetAddress.java:1276)
at java.net.InetAddress.getAllByName(InetAddress.java:1192)
at java.net.InetAddress.getAllByName(InetAddress.java:1126)
at java.net.InetAddress.getByName(InetAddress.java:1076)
at TestBadIpAddress.main(TestBadIpAddress.java:13)
On Sun, Aug 28, 2016 at 9:25 PM, Bryan Rosander <br...@gmail.com>
wrote:
> Downloaded source
>
> Verified checksums
>
> Ran build with contrib-check and empty local repo
>
> Ran build with –T2 concurrency and empty local repo
>
> Used tls-toolkit to generate 4 localhost keystore, truststore,
> nifi.properties and a single client certificate
>
> Started all 4 instances verified no port conflicts, correct certificate
> usage
>
> Imported CA certificate, client cert into browser, verified tls working
> properly
>
> +1 (non-binding)
>
> Thanks,
> Bryan
>
> On Aug 28, 2016 7:30 PM, "Tony Kurc" <tr...@gmail.com> wrote:
>
> > +1 (binding)
> >
> > Full build starting with empty maven repository on Ubuntu 14.04 (x86_64)
> > successfully.
> >
> > Verified signatures and hashes. Reviewed LICENSE/NOTICE.
> >
> > Ran a simple flow with no issues. Ran a few nifi-toolkit commands.
> >
> >
> >
> > On Sun, Aug 28, 2016 at 5:29 PM, Joe Witt <jo...@gmail.com> wrote:
> >
> > > +1 (binding)
> > >
> > > Full clean build w/contrib check good.
> > >
> > > Verified signatures (and strength), hashes, and LICENSE/NOTICE within
> > > sources and convenience binaries.
> > >
> > > Verified the commit the release was based on.
> > >
> > > Ran single and multi-node clusters with favorable results.
> > >
> > > For future release please do move any necessary elements of the UnRar
> > > item to NOTICE where category B items belong. See here for LEGAL
> > > discuss https://issues.apache.org/jira/browse/LEGAL-52 on this.
> > >
> > > Great job pulling the release together again JoeP.
> > >
> > > Thanks
> > > Joe
> > >
> > > On Fri, Aug 26, 2016 at 12:25 PM, Joe Percivall
> > > <jo...@yahoo.com.invalid> wrote:
> > > > Hello Apache NiFi Community,
> > > >
> > > > I am pleased to be calling this vote for the source release of Apache
> > > NiFi,
> > > > nifi-1.0.0.
> > > >
> > > > The source zip, including signatures, digests, etc. can be found at:
> > > > https://repository.apache.org/content/repositories/
> orgapachenifi-1090/
> > > >
> > > > Note: There is a second binary being distributed now, the NiFi
> Toolkit.
> > > It
> > > > can be used to facilitate securing a NiFi instance.
> > > >
> > > > The Git tag is nifi-1.0.0-RC1
> > > > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > > 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > > * https://github.com/apache/nifi/commit/
> 74d5224783dfdc513f6b3ad5ed9667
> > > 1d3c581707
> > > >
> > > > Checksums of nifi-1.0.0-source-release.zip:
> > > > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> > > > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> > > > SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447
> > af92
> > > >
> > > > Release artifacts are signed with the following key:
> > > > https://people.apache.org/keys/committer/jpercivall
> > > >
> > > > KEYS file available here:
> > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > >
> > > > 595 issues were closed/resolved for this release:
> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > projectId=12316020&version=12332640
> > > >
> > > > Release note highlights can be found here:
> > > > https://cwiki.apache.org/confluence/display/NIFI/
> > > Release+Notes#ReleaseNotes-Version1.0.0
> > > >
> > > > The vote will be open for 72 hours.
> > > > Please download the release candidate and evaluate the necessary
> items
> > > > including checking hashes, signatures, build from source, and test.
> > Then
> > > > please vote:
> > > >
> > > > [ ] +1 Release this package as nifi-1.0.0
> > > > [ ] +0 no opinion
> > > > [ ] -1 Do not release this package because...
> > > >
> > > > Thanks!
> > >
> >
>
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Bryan Rosander <br...@gmail.com>.
Downloaded source
Verified checksums
Ran build with contrib-check and empty local repo
Ran build with –T2 concurrency and empty local repo
Used tls-toolkit to generate 4 localhost keystore, truststore,
nifi.properties and a single client certificate
Started all 4 instances verified no port conflicts, correct certificate
usage
Imported CA certificate, client cert into browser, verified tls working
properly
+1 (non-binding)
Thanks,
Bryan
On Aug 28, 2016 7:30 PM, "Tony Kurc" <tr...@gmail.com> wrote:
> +1 (binding)
>
> Full build starting with empty maven repository on Ubuntu 14.04 (x86_64)
> successfully.
>
> Verified signatures and hashes. Reviewed LICENSE/NOTICE.
>
> Ran a simple flow with no issues. Ran a few nifi-toolkit commands.
>
>
>
> On Sun, Aug 28, 2016 at 5:29 PM, Joe Witt <jo...@gmail.com> wrote:
>
> > +1 (binding)
> >
> > Full clean build w/contrib check good.
> >
> > Verified signatures (and strength), hashes, and LICENSE/NOTICE within
> > sources and convenience binaries.
> >
> > Verified the commit the release was based on.
> >
> > Ran single and multi-node clusters with favorable results.
> >
> > For future release please do move any necessary elements of the UnRar
> > item to NOTICE where category B items belong. See here for LEGAL
> > discuss https://issues.apache.org/jira/browse/LEGAL-52 on this.
> >
> > Great job pulling the release together again JoeP.
> >
> > Thanks
> > Joe
> >
> > On Fri, Aug 26, 2016 at 12:25 PM, Joe Percivall
> > <jo...@yahoo.com.invalid> wrote:
> > > Hello Apache NiFi Community,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > NiFi,
> > > nifi-1.0.0.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1090/
> > >
> > > Note: There is a second binary being distributed now, the NiFi Toolkit.
> > It
> > > can be used to facilitate securing a NiFi instance.
> > >
> > > The Git tag is nifi-1.0.0-RC1
> > > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > > * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3ad5ed9667
> > 1d3c581707
> > >
> > > Checksums of nifi-1.0.0-source-release.zip:
> > > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> > > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> > > SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447
> af92
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/jpercivall
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 595 issues were closed/resolved for this release:
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12316020&version=12332640
> > >
> > > Release note highlights can be found here:
> > > https://cwiki.apache.org/confluence/display/NIFI/
> > Release+Notes#ReleaseNotes-Version1.0.0
> > >
> > > The vote will be open for 72 hours.
> > > Please download the release candidate and evaluate the necessary items
> > > including checking hashes, signatures, build from source, and test.
> Then
> > > please vote:
> > >
> > > [ ] +1 Release this package as nifi-1.0.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
> > > Thanks!
> >
>
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Tony Kurc <tr...@gmail.com>.
+1 (binding)
Full build starting with empty maven repository on Ubuntu 14.04 (x86_64)
successfully.
Verified signatures and hashes. Reviewed LICENSE/NOTICE.
Ran a simple flow with no issues. Ran a few nifi-toolkit commands.
On Sun, Aug 28, 2016 at 5:29 PM, Joe Witt <jo...@gmail.com> wrote:
> +1 (binding)
>
> Full clean build w/contrib check good.
>
> Verified signatures (and strength), hashes, and LICENSE/NOTICE within
> sources and convenience binaries.
>
> Verified the commit the release was based on.
>
> Ran single and multi-node clusters with favorable results.
>
> For future release please do move any necessary elements of the UnRar
> item to NOTICE where category B items belong. See here for LEGAL
> discuss https://issues.apache.org/jira/browse/LEGAL-52 on this.
>
> Great job pulling the release together again JoeP.
>
> Thanks
> Joe
>
> On Fri, Aug 26, 2016 at 12:25 PM, Joe Percivall
> <jo...@yahoo.com.invalid> wrote:
> > Hello Apache NiFi Community,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi,
> > nifi-1.0.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1090/
> >
> > Note: There is a second binary being distributed now, the NiFi Toolkit.
> It
> > can be used to facilitate securing a NiFi instance.
> >
> > The Git tag is nifi-1.0.0-RC1
> > The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> 74d5224783dfdc513f6b3ad5ed96671d3c581707
> > * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3ad5ed9667
> 1d3c581707
> >
> > Checksums of nifi-1.0.0-source-release.zip:
> > MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> > SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> > SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/jpercivall
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 595 issues were closed/resolved for this release:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12316020&version=12332640
> >
> > Release note highlights can be found here:
> > https://cwiki.apache.org/confluence/display/NIFI/
> Release+Notes#ReleaseNotes-Version1.0.0
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test. Then
> > please vote:
> >
> > [ ] +1 Release this package as nifi-1.0.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks!
>
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Joe Witt <jo...@gmail.com>.
+1 (binding)
Full clean build w/contrib check good.
Verified signatures (and strength), hashes, and LICENSE/NOTICE within
sources and convenience binaries.
Verified the commit the release was based on.
Ran single and multi-node clusters with favorable results.
For future release please do move any necessary elements of the UnRar
item to NOTICE where category B items belong. See here for LEGAL
discuss https://issues.apache.org/jira/browse/LEGAL-52 on this.
Great job pulling the release together again JoeP.
Thanks
Joe
On Fri, Aug 26, 2016 at 12:25 PM, Joe Percivall
<jo...@yahoo.com.invalid> wrote:
> Hello Apache NiFi Community,
>
> I am pleased to be calling this vote for the source release of Apache NiFi,
> nifi-1.0.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1090/
>
> Note: There is a second binary being distributed now, the NiFi Toolkit. It
> can be used to facilitate securing a NiFi instance.
>
> The Git tag is nifi-1.0.0-RC1
> The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=74d5224783dfdc513f6b3ad5ed96671d3c581707
> * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3ad5ed96671d3c581707
>
> Checksums of nifi-1.0.0-source-release.zip:
> MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/jpercivall
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 595 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12332640
>
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.0.0
>
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test. Then
> please vote:
>
> [ ] +1 Release this package as nifi-1.0.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> Thanks!
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Joe Skora <js...@gmail.com>.
@Pierre, if you don't want it I'd turn off updates, I did NOT get any
special notice until after it had installed.
On Mon, Aug 29, 2016 at 8:09 AM, Pierre Villard <pierre.villard.fr@gmail.com
> wrote:
> @Joe I don't have the anniversary update yet.
>
> 2016-08-29 13:56 GMT+02:00 Joe Skora <js...@gmail.com>:
>
> > To followup, the TestListenSMTP timeout problems got much better when I
> > changed a questionable DNS setting on the router. They still won't pass
> > within the 5 seconds currently configured in the test, but it was a
> > dramatic change.
> >
> > I was glad to see I wasn't the only one with this problem.
> >
> > Aldrin and Pierre, are you building on Windows 10 before or after the
> > anniversary update?
> >
> > On Mon, Aug 29, 2016 at 4:45 AM, Andy LoPresto <
> alopresto.apache@gmail.com
> > >
> > wrote:
> >
> > > Pierre and Andre,
> > >
> > > Thanks for reporting the issue where I forgot that some European and
> > > Australian time zones are represented as 4 characters. Obviously the
> test
> > > is overly specific with the regex, as the purpose is to ensure that the
> > > first serialized line is the date and time, and that is still true.
> I'll
> > > take a look at Andre's PR, but it should be an easy fix. Just another
> > > example of i18n biting us. I'll make more of an effort to test with an
> > eye
> > > towards global users from now on.
> > >
> > > Andy LoPresto
> > > alopresto@apache.org
> > > alopresto.apache@gmail.com
> > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> > >
> > > > On Aug 28, 2016, at 22:47, Pierre Villard <
> pierre.villard.fr@gmail.com
> > >
> > > wrote:
> > > >
> > > > +1 (non-binding)
> > > >
> > > > Full build with contrib-check on Mac OSX, Windows 10 and CentOS 7.
> > > >
> > > > I had the same issue as reported by Joe on SMTP tests with Windows 10
> > > > build. Workaround with timeouts works.
> > > >
> > > > I also reported two minor issues related to timezones (NIFI-2682) /
> > > locale
> > > > (NIFI-2683) aspects.
> > > > NIFI-2682 is a duplicate of NIFI-2688 created by Andre.
> > > >
> > > > I ran multiple workflows with a single instance and a three nodes
> > > cluster.
> > > > Checked failover scenario for clustering and exchanges with Kafka
> > > > 0.8/0.9/0.10, with HDFS and with Hive.
> > > >
> > > > Great job!
> > > >
> > > >
> > > > 2016-08-29 7:26 GMT+02:00 Andre <an...@fucs.org>:
> > > >
> > > >> created NIFI-2688 and PR963(master) and PR964 (RC1) to address the
> > regex
> > > >> issue.
> > > >>
> > > >>
> > > >>
> > > >>> On Mon, Aug 29, 2016 at 3:07 PM, Andre <an...@fucs.org>
> wrote:
> > > >>>
> > > >>> All,
> > > >>>
> > > >>> Had a look in the groovy code and reason is quite obvious:
> > > >>>
> > > >>> System locale does not match what the code expects via regex.
> > > >>
> > >
> >
>
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Pierre Villard <pi...@gmail.com>.
@Joe I don't have the anniversary update yet.
2016-08-29 13:56 GMT+02:00 Joe Skora <js...@gmail.com>:
> To followup, the TestListenSMTP timeout problems got much better when I
> changed a questionable DNS setting on the router. They still won't pass
> within the 5 seconds currently configured in the test, but it was a
> dramatic change.
>
> I was glad to see I wasn't the only one with this problem.
>
> Aldrin and Pierre, are you building on Windows 10 before or after the
> anniversary update?
>
> On Mon, Aug 29, 2016 at 4:45 AM, Andy LoPresto <alopresto.apache@gmail.com
> >
> wrote:
>
> > Pierre and Andre,
> >
> > Thanks for reporting the issue where I forgot that some European and
> > Australian time zones are represented as 4 characters. Obviously the test
> > is overly specific with the regex, as the purpose is to ensure that the
> > first serialized line is the date and time, and that is still true. I'll
> > take a look at Andre's PR, but it should be an easy fix. Just another
> > example of i18n biting us. I'll make more of an effort to test with an
> eye
> > towards global users from now on.
> >
> > Andy LoPresto
> > alopresto@apache.org
> > alopresto.apache@gmail.com
> > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> >
> > > On Aug 28, 2016, at 22:47, Pierre Villard <pierre.villard.fr@gmail.com
> >
> > wrote:
> > >
> > > +1 (non-binding)
> > >
> > > Full build with contrib-check on Mac OSX, Windows 10 and CentOS 7.
> > >
> > > I had the same issue as reported by Joe on SMTP tests with Windows 10
> > > build. Workaround with timeouts works.
> > >
> > > I also reported two minor issues related to timezones (NIFI-2682) /
> > locale
> > > (NIFI-2683) aspects.
> > > NIFI-2682 is a duplicate of NIFI-2688 created by Andre.
> > >
> > > I ran multiple workflows with a single instance and a three nodes
> > cluster.
> > > Checked failover scenario for clustering and exchanges with Kafka
> > > 0.8/0.9/0.10, with HDFS and with Hive.
> > >
> > > Great job!
> > >
> > >
> > > 2016-08-29 7:26 GMT+02:00 Andre <an...@fucs.org>:
> > >
> > >> created NIFI-2688 and PR963(master) and PR964 (RC1) to address the
> regex
> > >> issue.
> > >>
> > >>
> > >>
> > >>> On Mon, Aug 29, 2016 at 3:07 PM, Andre <an...@fucs.org> wrote:
> > >>>
> > >>> All,
> > >>>
> > >>> Had a look in the groovy code and reason is quite obvious:
> > >>>
> > >>> System locale does not match what the code expects via regex.
> > >>
> >
>
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Joe Skora <js...@gmail.com>.
To followup, the TestListenSMTP timeout problems got much better when I
changed a questionable DNS setting on the router. They still won't pass
within the 5 seconds currently configured in the test, but it was a
dramatic change.
I was glad to see I wasn't the only one with this problem.
Aldrin and Pierre, are you building on Windows 10 before or after the
anniversary update?
On Mon, Aug 29, 2016 at 4:45 AM, Andy LoPresto <al...@gmail.com>
wrote:
> Pierre and Andre,
>
> Thanks for reporting the issue where I forgot that some European and
> Australian time zones are represented as 4 characters. Obviously the test
> is overly specific with the regex, as the purpose is to ensure that the
> first serialized line is the date and time, and that is still true. I'll
> take a look at Andre's PR, but it should be an easy fix. Just another
> example of i18n biting us. I'll make more of an effort to test with an eye
> towards global users from now on.
>
> Andy LoPresto
> alopresto@apache.org
> alopresto.apache@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>
> > On Aug 28, 2016, at 22:47, Pierre Villard <pi...@gmail.com>
> wrote:
> >
> > +1 (non-binding)
> >
> > Full build with contrib-check on Mac OSX, Windows 10 and CentOS 7.
> >
> > I had the same issue as reported by Joe on SMTP tests with Windows 10
> > build. Workaround with timeouts works.
> >
> > I also reported two minor issues related to timezones (NIFI-2682) /
> locale
> > (NIFI-2683) aspects.
> > NIFI-2682 is a duplicate of NIFI-2688 created by Andre.
> >
> > I ran multiple workflows with a single instance and a three nodes
> cluster.
> > Checked failover scenario for clustering and exchanges with Kafka
> > 0.8/0.9/0.10, with HDFS and with Hive.
> >
> > Great job!
> >
> >
> > 2016-08-29 7:26 GMT+02:00 Andre <an...@fucs.org>:
> >
> >> created NIFI-2688 and PR963(master) and PR964 (RC1) to address the regex
> >> issue.
> >>
> >>
> >>
> >>> On Mon, Aug 29, 2016 at 3:07 PM, Andre <an...@fucs.org> wrote:
> >>>
> >>> All,
> >>>
> >>> Had a look in the groovy code and reason is quite obvious:
> >>>
> >>> System locale does not match what the code expects via regex.
> >>
>
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Andy LoPresto <al...@gmail.com>.
Pierre and Andre,
Thanks for reporting the issue where I forgot that some European and Australian time zones are represented as 4 characters. Obviously the test is overly specific with the regex, as the purpose is to ensure that the first serialized line is the date and time, and that is still true. I'll take a look at Andre's PR, but it should be an easy fix. Just another example of i18n biting us. I'll make more of an effort to test with an eye towards global users from now on.
Andy LoPresto
alopresto@apache.org
alopresto.apache@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On Aug 28, 2016, at 22:47, Pierre Villard <pi...@gmail.com> wrote:
>
> +1 (non-binding)
>
> Full build with contrib-check on Mac OSX, Windows 10 and CentOS 7.
>
> I had the same issue as reported by Joe on SMTP tests with Windows 10
> build. Workaround with timeouts works.
>
> I also reported two minor issues related to timezones (NIFI-2682) / locale
> (NIFI-2683) aspects.
> NIFI-2682 is a duplicate of NIFI-2688 created by Andre.
>
> I ran multiple workflows with a single instance and a three nodes cluster.
> Checked failover scenario for clustering and exchanges with Kafka
> 0.8/0.9/0.10, with HDFS and with Hive.
>
> Great job!
>
>
> 2016-08-29 7:26 GMT+02:00 Andre <an...@fucs.org>:
>
>> created NIFI-2688 and PR963(master) and PR964 (RC1) to address the regex
>> issue.
>>
>>
>>
>>> On Mon, Aug 29, 2016 at 3:07 PM, Andre <an...@fucs.org> wrote:
>>>
>>> All,
>>>
>>> Had a look in the groovy code and reason is quite obvious:
>>>
>>> System locale does not match what the code expects via regex.
>>
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Pierre Villard <pi...@gmail.com>.
+1 (non-binding)
Full build with contrib-check on Mac OSX, Windows 10 and CentOS 7.
I had the same issue as reported by Joe on SMTP tests with Windows 10
build. Workaround with timeouts works.
I also reported two minor issues related to timezones (NIFI-2682) / locale
(NIFI-2683) aspects.
NIFI-2682 is a duplicate of NIFI-2688 created by Andre.
I ran multiple workflows with a single instance and a three nodes cluster.
Checked failover scenario for clustering and exchanges with Kafka
0.8/0.9/0.10, with HDFS and with Hive.
Great job!
2016-08-29 7:26 GMT+02:00 Andre <an...@fucs.org>:
> created NIFI-2688 and PR963(master) and PR964 (RC1) to address the regex
> issue.
>
>
>
> On Mon, Aug 29, 2016 at 3:07 PM, Andre <an...@fucs.org> wrote:
>
> > All,
> >
> > Had a look in the groovy code and reason is quite obvious:
> >
> > System locale does not match what the code expects via regex.
> >
> >
> >
>
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Koji Kawamura <ij...@gmail.com>.
Full clean build w/contrib check good.
Ran standalone NiFi and secured standalone.
-0.9 (non-binding)
Because I found two issues during the test.
1. Confusing log message with tls-toolkit.sh "No hostnames specified"
This is a trivial one, and this is NOT the reason why I did negative
fraction vote. The tls-toolkit.sh works functionally fine, but it logs
an INFO msg that is confusing to users. PR 965 is sent and ready to be
reviewed.
https://issues.apache.org/jira/browse/NIFI-2686
2. RPGPort REST endpoint tries to retrieve RPG with RPGPort ID
This is more critical issue, because it blocks users to enable/disable
RPG transmission per port.
Even if we left this, Site-to-Site can be used, but cannot control per
port basis.
I prefer this fix to be in 1.0.0, but I'd like to let Joe, release
manager decide.
PR 962 is ready for review.
https://issues.apache.org/jira/browse/NIFI-2687
Thanks,
Koji
On Mon, Aug 29, 2016 at 2:26 PM, Andre <an...@fucs.org> wrote:
> created NIFI-2688 and PR963(master) and PR964 (RC1) to address the regex
> issue.
>
>
>
> On Mon, Aug 29, 2016 at 3:07 PM, Andre <an...@fucs.org> wrote:
>
>> All,
>>
>> Had a look in the groovy code and reason is quite obvious:
>>
>> System locale does not match what the code expects via regex.
>>
>>
>>
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Andre <an...@fucs.org>.
created NIFI-2688 and PR963(master) and PR964 (RC1) to address the regex
issue.
On Mon, Aug 29, 2016 at 3:07 PM, Andre <an...@fucs.org> wrote:
> All,
>
> Had a look in the groovy code and reason is quite obvious:
>
> System locale does not match what the code expects via regex.
>
>
>
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Andre <an...@fucs.org>.
All,
Had a look in the groovy code and reason is quite obvious:
System locale does not match what the code expects via regex.
Re: [VOTE] Release Apache NiFi 1.0.0 (RC1)
Posted by Andre <an...@fucs.org>.
Joe,
I am having facing two build errors:
One I haven't figured out what causes:
testShouldSerializeNiFiProperties(org.apache.nifi.properties.ConfigEncryptionToolTest)
Time elapsed: 0.043 sec <<< FAILURE!
org.codehaus.groovy.runtime.powerassert.PowerAssertionError: assert
lines.first() =~ datePattern
| | | |
| | | ^#\w{3} \w{3} \d{2} \d{2}:\d{2}:\d{2}
\w{3}([\-+]\d{2}:\d{2})? \d{4}$
| | java.util.regex.Matcher[pattern=^#\w{3} \w{3} \d{2}
\d{2}:\d{2}:\d{2} \w{3}([\-+]\d{2}:\d{2})? \d{4}$ region=0,30 lastmatch=]
| #Fri Aug 26 16:50:13 AEST 2016
[#Fri Aug 26 16:50:13 AEST 2016, key=value, key2=value2]
at
org.codehaus.groovy.runtime.InvokerHelper.assertFailed(InvokerHelper.java:402)
at
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.assertFailed(ScriptBytecodeAdapter.java:650)
at
org.apache.nifi.properties.ConfigEncryptionToolTest.testShouldSerializeNiFiProperties(ConfigEncryptionToolTest.groovy:978)
The other is tracked on NIFI-2685 (PR960 against RC1 and PR961 against
master):
testResize(org.apache.nifi.processors.image.TestResizeImage) Time elapsed:
2.22 sec <<< FAILURE!
java.lang.AssertionError: java.awt.AWTError: Can't connect to X11 window
server using 'localhost:12.0' as the value of the DISPLAY variable.
On Sat, Aug 27, 2016 at 2:25 AM, Joe Percivall <
joepercivall@yahoo.com.invalid> wrote:
> Hello Apache NiFi Community,
>
> I am pleased to be calling this vote for the source release of Apache NiFi,
> nifi-1.0.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1090/
>
> Note: There is a second binary being distributed now, the NiFi Toolkit. It
> can be used to facilitate securing a NiFi instance.
>
> The Git tag is nifi-1.0.0-RC1
> The Git commit hash is 74d5224783dfdc513f6b3ad5ed96671d3c581707
> * https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> 74d5224783dfdc513f6b3ad5ed96671d3c581707
> * https://github.com/apache/nifi/commit/74d5224783dfdc513f6b3ad5ed9667
> 1d3c581707
>
> Checksums of nifi-1.0.0-source-release.zip:
> MD5: 8bdba49a73b94d036fad6c63b0ebe39d
> SHA1: 504c58f9b2fb305c41598a17f5b78f68f2b2fa3d
> SHA256: 22167ede5127683ca8de6dbd2fb9112cb1de650b7cfff7e640c905521447af92
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/jpercivall
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 595 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12316020&version=12332640
>
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/
> Release+Notes#ReleaseNotes-Version1.0.0
>
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test. Then
> please vote:
>
> [ ] +1 Release this package as nifi-1.0.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> Thanks!
>