Re: Question about ListenTCP processor
Paul, Of note, the processor already has a property for configuring the delimiter to use. Thanks -Mark > On Jan 27, 2021, at 12:53 AM, Otto Fowler wrote: > > It is in the base class > https://github.com/apache/nifi/blob/aa741cc5967f62c3c38c2a47e712b7faa6fe19ff/nifi-nar-bundles/nifi-extension-utils/nifi-processor-utils/src/main/java/org/apache/nifi/processor/util/listen/AbstractListenEventBatchingProcessor.java#L50 > >> On Jan 26, 2021, at 21:31, Hodor, Paul >> wrote: >> >> One of the constraints of the ListenTCP processor is that it delimites >> incoming data by the “line feed” or “newline” character. I am looking at its >> source code at >> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ListenTCP.java. >> Could you give me a hint where this constraint is defined. I don’s see it >> in the processor source code, so I assume it must come from another class >> that is being used. >> >> The reason I am asking is because we are trying to modify the processor to >> use a different delimiter character. >> >> Thanks, >> Paul >> >> >> CONFIDENTIALITY NOTICE: This e-mail, including any attachments, is for the >> sole use of the intended recipient(s) and may contain confidential and >> privileged information protected by law. Any unauthorized review, use, >> disclosure or distribution is prohibited. If you are not the intended >> recipient, please contact the sender by reply e-mail and destroy all copies >> of the original message. >
Re: [VOTE] Release Apache NiFi 1.13.0
+1 Followed the guide, built and ran, verified some of the new processor documentation. Note: was able to get this to build with : Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec Java version: 1.8.0_282, vendor: AdoptOpenJDK, runtime: /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.16", arch: "x86_64", family: “mac" but NOT with: Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec Java version: 1.8.0_171, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk1.8.0_171.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.16", arch: "x86_64", family: “mac” > On Jan 27, 2021, at 23:15, Joe Witt wrote: > > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > 1.13.0. > > The source zip, including signatures, digests, etc. can be found at: > https://repository.apache.org/content/repositories/orgapachenifi-1175 > > The source being voted upon and the convenience binaries can be found at: > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.13.0/ > > A helpful reminder on how the release candidate verification process works: > https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate > > The Git tag is nifi-1.13.0-RC1 > The Git commit ID is be1ac1c49726f366423b28fe75a08cbe9885ada3 > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=be1ac1c49726f366423b28fe75a08cbe9885ada3 > > Checksums of nifi-1.13.0-source-release.zip: > SHA256: 02f5cfff3a3c2a82f82270b03e3533449330d9fbc102da8e920ab0cb39361218 > SHA512: > 84769ec5791b6af1e9bca3088d535a611457ac13d046191021faf7c40ea0f1fc31238de43b9349e8034c2ec7d0cfeb570880fd9d4e6575d88ec52042b9fd997a > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/joewitt.asc > > KEYS file available here: > https://dist.apache.org/repos/dist/release/nifi/KEYS > > 228 issues were closed/resolved for this release: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12348700 > > Release note highlights can be found here: > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.13.0 > > Please note the convenience binary tar.gz and zip provided for NiFi include > one less nar (the 'nifi-ignite-nar') to ensure the total file size remains > under the ASF infrastructure limit. The migration guide and nifi-assembly > have been updated so explicit removal won't be necessary in the future. > But we will need to remain careful about any growth of our binaries and > will need to continue to prune out old nars until we move to another model > for users to acquire the nars they need. > > 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.13.0 > [ ] +0 no opinion > [ ] -1 Do not release this package because...
Re: [DISCUSS] Release of Apache NiFi 1.13.0
Otto Truth is we dont know. We cannot readily test with the amazing matrix that exists. So we are leaning toward ensuring recent versions work as expected. The goal is java 8 and 11 broadly right now. But these internal changes of exception types being used are brutal. Thanks On Thu, Jan 28, 2021 at 8:15 AM Otto Fowler wrote: > Thanks Joe, > > I’m started down that road right after I sent this. I’ll update when I > know. > I _have_ been building nifi with this jdk all along though. > > If there are jdk minimum requirements, should they be documented ( or are > they and I missed it)? > > > On Jan 28, 2021, at 09:35, Joe Witt wrote: > > > > Otto > > > > I dont know we can keep all variants of Java 8 happy. That one is nearly > > three years old. I would say try with something more recent. It has > been > > pretty shocking how many api changes we have seen across these builds. > > > > Thanks > > > > On Thu, Jan 28, 2021 at 6:12 AM Otto Fowler > wrote: > > > >> I’m trying to validate RC-1 and I’m seeing this exception building / > >> running tests > >> > >> [INFO] Running org.apache.nifi.processors.standard.TestListenTCP > >> [ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: > >> 4.499 s <<< FAILURE! - in > org.apache.nifi.processors.standard.TestListenTCP > >> [ERROR] > >> > testTLSClientAuthRequiredAndClientCertNotProvided(org.apache.nifi.processors.standard.TestListenTCP) > >> Time elapsed: 0.127 s <<< FAILURE! > >> java.lang.AssertionError: unexpected exception type thrown; > >> expected: but was: > >>at > >> > org.apache.nifi.processors.standard.TestListenTCP.testTLSClientAuthRequiredAndClientCertNotProvided(TestListenTCP.java:159) > >> Caused by: java.net.SocketException: Connection reset > >>at > >> > org.apache.nifi.processors.standard.TestListenTCP.runTCP(TestListenTCP.java:209) > >>at > >> > org.apache.nifi.processors.standard.TestListenTCP.lambda$testTLSClientAuthRequiredAndClientCertNotProvided$0(TestListenTCP.java:160) > >>at > >> > org.apache.nifi.processors.standard.TestListenTCP.testTLSClientAuthRequiredAndClientCertNotProvided(TestListenTCP.java:159) > >> > >> > >> > >> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) > >> Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec > >> Java version: 1.8.0_171, vendor: Oracle Corporation, runtime: > >> /Library/Java/JavaVirtualMachines/jdk1.8.0_171.jdk/Contents/Home/jre > >> Default locale: en_US, platform encoding: UTF-8 > >> OS name: "mac os x", version: "10.16", arch: "x86_64", family: “mac" > >> > >> > >> > >>> On Jan 27, 2021, at 10:31, Joe Witt wrote: > >>> > >>> ...in this brutal game of wach a mole another couple brittle tests have > >>> emerged on the Java 11 line. > >>> https://issues.apache.org/jira/browse/NIFI-8177 will get that looked > >> into. > >>> And I'm also seeing if for some reason adding a bit more horsepower/cpu > >>> usage to the github tests will help. Things had been very stable for > >> quite > >>> a while until the update to the latest 11.0.10 azul jdk came out so > kind > >> of > >>> strange the tests became less reliable then. Anyway dont want to > initiate > >>> the RC until things seem stable otherwise it makes the vote process > more > >>> difficult and further when the builds dont pass it makes the already > >>> difficult task of staying apace with PRs more inivolved. > >>> > >>> Thanks > >>> > >>> On Wed, Jan 27, 2021 at 12:19 AM Pierre Villard < > >> pierre.villard...@gmail.com> > >>> wrote: > >>> > Awesome, thanks Joe! > > Le mer. 27 janv. 2021 à 10:16, Joe Witt a écrit > : > > > Team, > > > > Ok wow so the issue with build failures that emerged has been > resolved > >> it > > appears thanks to a lot of effort by exceptionfactory. The other > lingering > > commits/PRs are in and I think most of what folks asked for in this > > thread. I just put in a commit which drops a few older/less common > >> nars > > from convenience binary inclusion to get us back under the maximum > size > > again. And now I think we can initiate RC1 build for 1.13.0. > > > > That should be published in the AM. > > > > Thanks > > > > On Mon, Jan 25, 2021 at 6:40 AM Joe Witt wrote: > > > >> Team, > >> > >> There is a TZ handling issue > >> https://issues.apache.org/jira/browse/NIFI-8023 that needs a > resolution > >> and there is also a new issue that has emerged on Github Actions/CI > >> https://github.com/apache/nifi/actions which is resulting in broken > >> builds. This emerged in the latest Java 11 Azul release and in > Github > > CI. > >> I've tried to replicate with no success on a local linux machine > with > the > >> exact same JVM/version. > >> > >> Once these are wrapped I'll initiate the RC. Great work to all > involved > >> in helping get the release candidate this close. > >> > >> T
Re: [DISCUSS] Release of Apache NiFi 1.13.0
Although I _have_ been building with this jdk for a long time, I may not have built with it since the TLS changes when it. Maybe that is a factor. > On Jan 28, 2021, at 10:15, Otto Fowler wrote: > > Thanks Joe, > > I’m started down that road right after I sent this. I’ll update when I know. > I _have_ been building nifi with this jdk all along though. > > If there are jdk minimum requirements, should they be documented ( or are > they and I missed it)? > >> On Jan 28, 2021, at 09:35, Joe Witt wrote: >> >> Otto >> >> I dont know we can keep all variants of Java 8 happy. That one is nearly >> three years old. I would say try with something more recent. It has been >> pretty shocking how many api changes we have seen across these builds. >> >> Thanks >> >> On Thu, Jan 28, 2021 at 6:12 AM Otto Fowler wrote: >> >>> I’m trying to validate RC-1 and I’m seeing this exception building / >>> running tests >>> >>> [INFO] Running org.apache.nifi.processors.standard.TestListenTCP >>> [ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: >>> 4.499 s <<< FAILURE! - in org.apache.nifi.processors.standard.TestListenTCP >>> [ERROR] >>> testTLSClientAuthRequiredAndClientCertNotProvided(org.apache.nifi.processors.standard.TestListenTCP) >>> Time elapsed: 0.127 s <<< FAILURE! >>> java.lang.AssertionError: unexpected exception type thrown; >>> expected: but was: >>> at >>> org.apache.nifi.processors.standard.TestListenTCP.testTLSClientAuthRequiredAndClientCertNotProvided(TestListenTCP.java:159) >>> Caused by: java.net.SocketException: Connection reset >>> at >>> org.apache.nifi.processors.standard.TestListenTCP.runTCP(TestListenTCP.java:209) >>> at >>> org.apache.nifi.processors.standard.TestListenTCP.lambda$testTLSClientAuthRequiredAndClientCertNotProvided$0(TestListenTCP.java:160) >>> at >>> org.apache.nifi.processors.standard.TestListenTCP.testTLSClientAuthRequiredAndClientCertNotProvided(TestListenTCP.java:159) >>> >>> >>> >>> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) >>> Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec >>> Java version: 1.8.0_171, vendor: Oracle Corporation, runtime: >>> /Library/Java/JavaVirtualMachines/jdk1.8.0_171.jdk/Contents/Home/jre >>> Default locale: en_US, platform encoding: UTF-8 >>> OS name: "mac os x", version: "10.16", arch: "x86_64", family: “mac" >>> >>> >>> On Jan 27, 2021, at 10:31, Joe Witt wrote: ...in this brutal game of wach a mole another couple brittle tests have emerged on the Java 11 line. https://issues.apache.org/jira/browse/NIFI-8177 will get that looked >>> into. And I'm also seeing if for some reason adding a bit more horsepower/cpu usage to the github tests will help. Things had been very stable for >>> quite a while until the update to the latest 11.0.10 azul jdk came out so kind >>> of strange the tests became less reliable then. Anyway dont want to initiate the RC until things seem stable otherwise it makes the vote process more difficult and further when the builds dont pass it makes the already difficult task of staying apace with PRs more inivolved. Thanks On Wed, Jan 27, 2021 at 12:19 AM Pierre Villard < >>> pierre.villard...@gmail.com> wrote: > Awesome, thanks Joe! > > Le mer. 27 janv. 2021 à 10:16, Joe Witt a écrit : > >> Team, >> >> Ok wow so the issue with build failures that emerged has been resolved >>> it >> appears thanks to a lot of effort by exceptionfactory. The other > lingering >> commits/PRs are in and I think most of what folks asked for in this >> thread. I just put in a commit which drops a few older/less common >>> nars >> from convenience binary inclusion to get us back under the maximum size >> again. And now I think we can initiate RC1 build for 1.13.0. >> >> That should be published in the AM. >> >> Thanks >> >> On Mon, Jan 25, 2021 at 6:40 AM Joe Witt wrote: >> >>> Team, >>> >>> There is a TZ handling issue >>> https://issues.apache.org/jira/browse/NIFI-8023 that needs a > resolution >>> and there is also a new issue that has emerged on Github Actions/CI >>> https://github.com/apache/nifi/actions which is resulting in broken >>> builds. This emerged in the latest Java 11 Azul release and in Github >> CI. >>> I've tried to replicate with no success on a local linux machine with > the >>> exact same JVM/version. >>> >>> Once these are wrapped I'll initiate the RC. Great work to all > involved >>> in helping get the release candidate this close. >>> >>> Thanks >>> Joe >>> >>> On Thu, Jan 21, 2021 at 8:30 AM Joe Witt wrote: >>> Team, A couple 1.13 tagged items still lingering. Going to either kick >>> them out or merge them and get going. Hop
Re: [DISCUSS] Release of Apache NiFi 1.13.0
Thanks Joe, I’m started down that road right after I sent this. I’ll update when I know. I _have_ been building nifi with this jdk all along though. If there are jdk minimum requirements, should they be documented ( or are they and I missed it)? > On Jan 28, 2021, at 09:35, Joe Witt wrote: > > Otto > > I dont know we can keep all variants of Java 8 happy. That one is nearly > three years old. I would say try with something more recent. It has been > pretty shocking how many api changes we have seen across these builds. > > Thanks > > On Thu, Jan 28, 2021 at 6:12 AM Otto Fowler wrote: > >> I’m trying to validate RC-1 and I’m seeing this exception building / >> running tests >> >> [INFO] Running org.apache.nifi.processors.standard.TestListenTCP >> [ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: >> 4.499 s <<< FAILURE! - in org.apache.nifi.processors.standard.TestListenTCP >> [ERROR] >> testTLSClientAuthRequiredAndClientCertNotProvided(org.apache.nifi.processors.standard.TestListenTCP) >> Time elapsed: 0.127 s <<< FAILURE! >> java.lang.AssertionError: unexpected exception type thrown; >> expected: but was: >>at >> org.apache.nifi.processors.standard.TestListenTCP.testTLSClientAuthRequiredAndClientCertNotProvided(TestListenTCP.java:159) >> Caused by: java.net.SocketException: Connection reset >>at >> org.apache.nifi.processors.standard.TestListenTCP.runTCP(TestListenTCP.java:209) >>at >> org.apache.nifi.processors.standard.TestListenTCP.lambda$testTLSClientAuthRequiredAndClientCertNotProvided$0(TestListenTCP.java:160) >>at >> org.apache.nifi.processors.standard.TestListenTCP.testTLSClientAuthRequiredAndClientCertNotProvided(TestListenTCP.java:159) >> >> >> >> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) >> Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec >> Java version: 1.8.0_171, vendor: Oracle Corporation, runtime: >> /Library/Java/JavaVirtualMachines/jdk1.8.0_171.jdk/Contents/Home/jre >> Default locale: en_US, platform encoding: UTF-8 >> OS name: "mac os x", version: "10.16", arch: "x86_64", family: “mac" >> >> >> >>> On Jan 27, 2021, at 10:31, Joe Witt wrote: >>> >>> ...in this brutal game of wach a mole another couple brittle tests have >>> emerged on the Java 11 line. >>> https://issues.apache.org/jira/browse/NIFI-8177 will get that looked >> into. >>> And I'm also seeing if for some reason adding a bit more horsepower/cpu >>> usage to the github tests will help. Things had been very stable for >> quite >>> a while until the update to the latest 11.0.10 azul jdk came out so kind >> of >>> strange the tests became less reliable then. Anyway dont want to initiate >>> the RC until things seem stable otherwise it makes the vote process more >>> difficult and further when the builds dont pass it makes the already >>> difficult task of staying apace with PRs more inivolved. >>> >>> Thanks >>> >>> On Wed, Jan 27, 2021 at 12:19 AM Pierre Villard < >> pierre.villard...@gmail.com> >>> wrote: >>> Awesome, thanks Joe! Le mer. 27 janv. 2021 à 10:16, Joe Witt a écrit : > Team, > > Ok wow so the issue with build failures that emerged has been resolved >> it > appears thanks to a lot of effort by exceptionfactory. The other lingering > commits/PRs are in and I think most of what folks asked for in this > thread. I just put in a commit which drops a few older/less common >> nars > from convenience binary inclusion to get us back under the maximum size > again. And now I think we can initiate RC1 build for 1.13.0. > > That should be published in the AM. > > Thanks > > On Mon, Jan 25, 2021 at 6:40 AM Joe Witt wrote: > >> Team, >> >> There is a TZ handling issue >> https://issues.apache.org/jira/browse/NIFI-8023 that needs a resolution >> and there is also a new issue that has emerged on Github Actions/CI >> https://github.com/apache/nifi/actions which is resulting in broken >> builds. This emerged in the latest Java 11 Azul release and in Github > CI. >> I've tried to replicate with no success on a local linux machine with the >> exact same JVM/version. >> >> Once these are wrapped I'll initiate the RC. Great work to all involved >> in helping get the release candidate this close. >> >> Thanks >> Joe >> >> On Thu, Jan 21, 2021 at 8:30 AM Joe Witt wrote: >> >>> Team, >>> >>> A couple 1.13 tagged items still lingering. Going to either kick >> them >>> out or merge them and get going. Hopefully an RC today or tomorrow. >>> >>> Thanks >>> >>> On Wed, Jan 20, 2021 at 7:21 AM Mike Thomsen >> >>> wrote: >>> Bug confirmed. Working on a PR now. On Wed, Jan 20, 2021 at 8:45 AM Mike Thomsen < >> mikerthom...@gmail.com > wrote: > > Th
Re: [DISCUSS] Release of Apache NiFi 1.13.0
Otto I dont know we can keep all variants of Java 8 happy. That one is nearly three years old. I would say try with something more recent. It has been pretty shocking how many api changes we have seen across these builds. Thanks On Thu, Jan 28, 2021 at 6:12 AM Otto Fowler wrote: > I’m trying to validate RC-1 and I’m seeing this exception building / > running tests > > [INFO] Running org.apache.nifi.processors.standard.TestListenTCP > [ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: > 4.499 s <<< FAILURE! - in org.apache.nifi.processors.standard.TestListenTCP > [ERROR] > testTLSClientAuthRequiredAndClientCertNotProvided(org.apache.nifi.processors.standard.TestListenTCP) > Time elapsed: 0.127 s <<< FAILURE! > java.lang.AssertionError: unexpected exception type thrown; > expected: but was: > at > org.apache.nifi.processors.standard.TestListenTCP.testTLSClientAuthRequiredAndClientCertNotProvided(TestListenTCP.java:159) > Caused by: java.net.SocketException: Connection reset > at > org.apache.nifi.processors.standard.TestListenTCP.runTCP(TestListenTCP.java:209) > at > org.apache.nifi.processors.standard.TestListenTCP.lambda$testTLSClientAuthRequiredAndClientCertNotProvided$0(TestListenTCP.java:160) > at > org.apache.nifi.processors.standard.TestListenTCP.testTLSClientAuthRequiredAndClientCertNotProvided(TestListenTCP.java:159) > > > > Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) > Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec > Java version: 1.8.0_171, vendor: Oracle Corporation, runtime: > /Library/Java/JavaVirtualMachines/jdk1.8.0_171.jdk/Contents/Home/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "10.16", arch: "x86_64", family: “mac" > > > > > On Jan 27, 2021, at 10:31, Joe Witt wrote: > > > > ...in this brutal game of wach a mole another couple brittle tests have > > emerged on the Java 11 line. > > https://issues.apache.org/jira/browse/NIFI-8177 will get that looked > into. > > And I'm also seeing if for some reason adding a bit more horsepower/cpu > > usage to the github tests will help. Things had been very stable for > quite > > a while until the update to the latest 11.0.10 azul jdk came out so kind > of > > strange the tests became less reliable then. Anyway dont want to initiate > > the RC until things seem stable otherwise it makes the vote process more > > difficult and further when the builds dont pass it makes the already > > difficult task of staying apace with PRs more inivolved. > > > > Thanks > > > > On Wed, Jan 27, 2021 at 12:19 AM Pierre Villard < > pierre.villard...@gmail.com> > > wrote: > > > >> Awesome, thanks Joe! > >> > >> Le mer. 27 janv. 2021 à 10:16, Joe Witt a écrit : > >> > >>> Team, > >>> > >>> Ok wow so the issue with build failures that emerged has been resolved > it > >>> appears thanks to a lot of effort by exceptionfactory. The other > >> lingering > >>> commits/PRs are in and I think most of what folks asked for in this > >>> thread. I just put in a commit which drops a few older/less common > nars > >>> from convenience binary inclusion to get us back under the maximum size > >>> again. And now I think we can initiate RC1 build for 1.13.0. > >>> > >>> That should be published in the AM. > >>> > >>> Thanks > >>> > >>> On Mon, Jan 25, 2021 at 6:40 AM Joe Witt wrote: > >>> > Team, > > There is a TZ handling issue > https://issues.apache.org/jira/browse/NIFI-8023 that needs a > >> resolution > and there is also a new issue that has emerged on Github Actions/CI > https://github.com/apache/nifi/actions which is resulting in broken > builds. This emerged in the latest Java 11 Azul release and in Github > >>> CI. > I've tried to replicate with no success on a local linux machine with > >> the > exact same JVM/version. > > Once these are wrapped I'll initiate the RC. Great work to all > >> involved > in helping get the release candidate this close. > > Thanks > Joe > > On Thu, Jan 21, 2021 at 8:30 AM Joe Witt wrote: > > > Team, > > > > A couple 1.13 tagged items still lingering. Going to either kick > them > > out or merge them and get going. Hopefully an RC today or tomorrow. > > > > Thanks > > > > On Wed, Jan 20, 2021 at 7:21 AM Mike Thomsen > > > wrote: > > > >> Bug confirmed. Working on a PR now. > >> > >> On Wed, Jan 20, 2021 at 8:45 AM Mike Thomsen < > mikerthom...@gmail.com > >>> > >> wrote: > >>> > >>> This morning, I think I found a serious bug in PutCassandraRecord > >> WRT > >>> writing binary data to Cassandra. I'm debugging now. If it's > >> really a > >>> bug, I'd appreciate it if we could squeak a fix into 1.13. > >>> > >>> On Tue, Jan 19, 2021 at 9:54 AM Joe Witt > >> wrote: > > Team, > > I'm going to initiate RM processes f
Re: [DISCUSS] Release of Apache NiFi 1.13.0
I’m trying to validate RC-1 and I’m seeing this exception building / running tests [INFO] Running org.apache.nifi.processors.standard.TestListenTCP [ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 4.499 s <<< FAILURE! - in org.apache.nifi.processors.standard.TestListenTCP [ERROR] testTLSClientAuthRequiredAndClientCertNotProvided(org.apache.nifi.processors.standard.TestListenTCP) Time elapsed: 0.127 s <<< FAILURE! java.lang.AssertionError: unexpected exception type thrown; expected: but was: at org.apache.nifi.processors.standard.TestListenTCP.testTLSClientAuthRequiredAndClientCertNotProvided(TestListenTCP.java:159) Caused by: java.net.SocketException: Connection reset at org.apache.nifi.processors.standard.TestListenTCP.runTCP(TestListenTCP.java:209) at org.apache.nifi.processors.standard.TestListenTCP.lambda$testTLSClientAuthRequiredAndClientCertNotProvided$0(TestListenTCP.java:160) at org.apache.nifi.processors.standard.TestListenTCP.testTLSClientAuthRequiredAndClientCertNotProvided(TestListenTCP.java:159) Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home: /usr/local/Cellar/maven/3.6.3_1/libexec Java version: 1.8.0_171, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk1.8.0_171.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.16", arch: "x86_64", family: “mac" > On Jan 27, 2021, at 10:31, Joe Witt wrote: > > ...in this brutal game of wach a mole another couple brittle tests have > emerged on the Java 11 line. > https://issues.apache.org/jira/browse/NIFI-8177 will get that looked into. > And I'm also seeing if for some reason adding a bit more horsepower/cpu > usage to the github tests will help. Things had been very stable for quite > a while until the update to the latest 11.0.10 azul jdk came out so kind of > strange the tests became less reliable then. Anyway dont want to initiate > the RC until things seem stable otherwise it makes the vote process more > difficult and further when the builds dont pass it makes the already > difficult task of staying apace with PRs more inivolved. > > Thanks > > On Wed, Jan 27, 2021 at 12:19 AM Pierre Villard > wrote: > >> Awesome, thanks Joe! >> >> Le mer. 27 janv. 2021 à 10:16, Joe Witt a écrit : >> >>> Team, >>> >>> Ok wow so the issue with build failures that emerged has been resolved it >>> appears thanks to a lot of effort by exceptionfactory. The other >> lingering >>> commits/PRs are in and I think most of what folks asked for in this >>> thread. I just put in a commit which drops a few older/less common nars >>> from convenience binary inclusion to get us back under the maximum size >>> again. And now I think we can initiate RC1 build for 1.13.0. >>> >>> That should be published in the AM. >>> >>> Thanks >>> >>> On Mon, Jan 25, 2021 at 6:40 AM Joe Witt wrote: >>> Team, There is a TZ handling issue https://issues.apache.org/jira/browse/NIFI-8023 that needs a >> resolution and there is also a new issue that has emerged on Github Actions/CI https://github.com/apache/nifi/actions which is resulting in broken builds. This emerged in the latest Java 11 Azul release and in Github >>> CI. I've tried to replicate with no success on a local linux machine with >> the exact same JVM/version. Once these are wrapped I'll initiate the RC. Great work to all >> involved in helping get the release candidate this close. Thanks Joe On Thu, Jan 21, 2021 at 8:30 AM Joe Witt wrote: > Team, > > A couple 1.13 tagged items still lingering. Going to either kick them > out or merge them and get going. Hopefully an RC today or tomorrow. > > Thanks > > On Wed, Jan 20, 2021 at 7:21 AM Mike Thomsen > wrote: > >> Bug confirmed. Working on a PR now. >> >> On Wed, Jan 20, 2021 at 8:45 AM Mike Thomsen >> >> wrote: >>> >>> This morning, I think I found a serious bug in PutCassandraRecord >> WRT >>> writing binary data to Cassandra. I'm debugging now. If it's >> really a >>> bug, I'd appreciate it if we could squeak a fix into 1.13. >>> >>> On Tue, Jan 19, 2021 at 9:54 AM Joe Witt >> wrote: Team, I'm going to initiate RM processes for 1.13. I'll be watching >> closely for currently tagged 1.13 items to include. If anything is dragging >> I'll just remove it from 1.13 and we'll pick it up later. Other items that >>> get dev/reviewer traction before I cut the RC we can include. I will *probably/hopefully* start that process first thing tomorrow >>> morning. https://issues.apache.org/jira/projects/NIFI/versions/12348700 >> is >> what i'm working from. Thanks On Fri, J
