Re: Duplicated dependencies

[David Handermann]

Dan,

The initial removal of duplicate dependencies sounds good on its own.
Enforcing the rules might take a bit more evaluation, so having it as a
separate issue seems like the best way forward.

Regards,
David Handermann

On Thu, Sep 29, 2022 at 5:11 PM Dan S  wrote:

> Should the ticket include in addition to the removal of the duplicate
> dependencies the enforcement rules or just focus on the removal of the
> duplicate dependencies?
>
> On Thu, Sep 29, 2022 at 5:56 PM David Handermann <
> exceptionfact...@apache.org> wrote:
>
> > Dan,
> >
> > Thanks for the text reference and clarification. With those details, yes,
> > it looks like the duplicates should be removed from the modules listed.
> > Feel free to create a Jira issue to address this, and we should also
> > consider implementing some enforcement to avoid future duplicates.
> >
> > Regards,
> > David Handermann
> >
> > On Thu, Sep 29, 2022 at 4:21 PM Dan S  wrote:
> >
> > > Sorry about that. I did not realize I could not include an image. Here
> > is a
> > > text version:
> > >
> > > Warning:(624, 10) Dependency is duplicated in file(s):
> > > nifi-zendesk-processors
> > > Warning:(629, 10) Dependency is duplicated in file(s):
> > > nifi-zendesk-processors
> > > Warning:(644, 10) Dependency is duplicated in file(s):
> > > minifi-c2-provider-cache, minifi-c2-provider-delegating,
> > > minifi-c2-provider-nifi-rest, minifi-c2-provider-util,
> > > nifi-azure-reporting-task, nifi-pgp-processors, nifi-pgp-service,
> > > nifi-registry-framework, nifi-registry-jetty,
> > > nifi-registry-revision-spring-jdbc, nifi-registry-aws-extensions,
> > > nifi-registry-ranger-plugin, and nifi-registry-toolkit-persistence
> > > Warning:(654, 10) Dependency is duplicated in file(s):
> > > nifi-system-test-suite
> > > Warning:(659, 10) Dependency is duplicated in file(s):
> > > nifi-registry-framework, nifi-registry-jetty, nifi-registry-properties,
> > > nifi-registry-security-utils, and nifi-registry-web-api
> > >
> > > On Thu, Sep 29, 2022 at 5:16 PM David Handermann <
> > > exceptionfact...@apache.org> wrote:
> > >
> > > > Dan,
> > > >
> > > > Thanks for asking about these dependencies. The attached image did
> not
> > > come
> > > > through to the list, but the XML snippet shows the standard test
> > > > dependencies. These dependencies are applied to all modules by
> design,
> > to
> > > > avoid unnecessary repetition in child modules.
> > > >
> > > > Regards,
> > > > David Handermann
> > > >
> > > > On Thu, Sep 29, 2022 at 4:06 PM Dan S  wrote:
> > > >
> > > > > When looking in the top level pom.xml in IntelliJ I see
> > > > >
> > > > > [image: image.png]
> > > > >
> > > > >
> > > > > The duplicate dependencies are:
> > > > > 
> > > > > org.junit.jupiter
> > > > > junit-jupiter-api
> > > > > test
> > > > > 
> > > > > 
> > > > > org.junit.jupiter
> > > > > junit-jupiter-engine
> > > > > test
> > > > > 
> > > > > 
> > > > > org.mockito
> > > > > mockito-core
> > > > > test
> > > > > 
> > > > > 
> > > > > org.slf4j
> > > > > slf4j-simple
> > > > > test
> > > > > 
> > > > > 
> > > > > org.codehaus.groovy
> > > > > groovy-test
> > > > > test
> > > > > 
> > > > >
> > > > > I assume these are oversites. Is this something a ticket should be
> > made
> > > > > for to fix?
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>

Re: Duplicated dependencies

[Dan S]

Should the ticket include in addition to the removal of the duplicate
dependencies the enforcement rules or just focus on the removal of the
duplicate dependencies?

On Thu, Sep 29, 2022 at 5:56 PM David Handermann <
exceptionfact...@apache.org> wrote:

> Dan,
>
> Thanks for the text reference and clarification. With those details, yes,
> it looks like the duplicates should be removed from the modules listed.
> Feel free to create a Jira issue to address this, and we should also
> consider implementing some enforcement to avoid future duplicates.
>
> Regards,
> David Handermann
>
> On Thu, Sep 29, 2022 at 4:21 PM Dan S  wrote:
>
> > Sorry about that. I did not realize I could not include an image. Here
> is a
> > text version:
> >
> > Warning:(624, 10) Dependency is duplicated in file(s):
> > nifi-zendesk-processors
> > Warning:(629, 10) Dependency is duplicated in file(s):
> > nifi-zendesk-processors
> > Warning:(644, 10) Dependency is duplicated in file(s):
> > minifi-c2-provider-cache, minifi-c2-provider-delegating,
> > minifi-c2-provider-nifi-rest, minifi-c2-provider-util,
> > nifi-azure-reporting-task, nifi-pgp-processors, nifi-pgp-service,
> > nifi-registry-framework, nifi-registry-jetty,
> > nifi-registry-revision-spring-jdbc, nifi-registry-aws-extensions,
> > nifi-registry-ranger-plugin, and nifi-registry-toolkit-persistence
> > Warning:(654, 10) Dependency is duplicated in file(s):
> > nifi-system-test-suite
> > Warning:(659, 10) Dependency is duplicated in file(s):
> > nifi-registry-framework, nifi-registry-jetty, nifi-registry-properties,
> > nifi-registry-security-utils, and nifi-registry-web-api
> >
> > On Thu, Sep 29, 2022 at 5:16 PM David Handermann <
> > exceptionfact...@apache.org> wrote:
> >
> > > Dan,
> > >
> > > Thanks for asking about these dependencies. The attached image did not
> > come
> > > through to the list, but the XML snippet shows the standard test
> > > dependencies. These dependencies are applied to all modules by design,
> to
> > > avoid unnecessary repetition in child modules.
> > >
> > > Regards,
> > > David Handermann
> > >
> > > On Thu, Sep 29, 2022 at 4:06 PM Dan S  wrote:
> > >
> > > > When looking in the top level pom.xml in IntelliJ I see
> > > >
> > > > [image: image.png]
> > > >
> > > >
> > > > The duplicate dependencies are:
> > > > 
> > > > org.junit.jupiter
> > > > junit-jupiter-api
> > > > test
> > > > 
> > > > 
> > > > org.junit.jupiter
> > > > junit-jupiter-engine
> > > > test
> > > > 
> > > > 
> > > > org.mockito
> > > > mockito-core
> > > > test
> > > > 
> > > > 
> > > > org.slf4j
> > > > slf4j-simple
> > > > test
> > > > 
> > > > 
> > > > org.codehaus.groovy
> > > > groovy-test
> > > > test
> > > > 
> > > >
> > > > I assume these are oversites. Is this something a ticket should be
> made
> > > > for to fix?
> > > >
> > > >
> > > >
> > > >
> > >
> >
>

Re: Duplicated dependencies

[David Handermann]

Dan,

Thanks for the text reference and clarification. With those details, yes,
it looks like the duplicates should be removed from the modules listed.
Feel free to create a Jira issue to address this, and we should also
consider implementing some enforcement to avoid future duplicates.

Regards,
David Handermann

On Thu, Sep 29, 2022 at 4:21 PM Dan S  wrote:

> Sorry about that. I did not realize I could not include an image. Here is a
> text version:
>
> Warning:(624, 10) Dependency is duplicated in file(s):
> nifi-zendesk-processors
> Warning:(629, 10) Dependency is duplicated in file(s):
> nifi-zendesk-processors
> Warning:(644, 10) Dependency is duplicated in file(s):
> minifi-c2-provider-cache, minifi-c2-provider-delegating,
> minifi-c2-provider-nifi-rest, minifi-c2-provider-util,
> nifi-azure-reporting-task, nifi-pgp-processors, nifi-pgp-service,
> nifi-registry-framework, nifi-registry-jetty,
> nifi-registry-revision-spring-jdbc, nifi-registry-aws-extensions,
> nifi-registry-ranger-plugin, and nifi-registry-toolkit-persistence
> Warning:(654, 10) Dependency is duplicated in file(s):
> nifi-system-test-suite
> Warning:(659, 10) Dependency is duplicated in file(s):
> nifi-registry-framework, nifi-registry-jetty, nifi-registry-properties,
> nifi-registry-security-utils, and nifi-registry-web-api
>
> On Thu, Sep 29, 2022 at 5:16 PM David Handermann <
> exceptionfact...@apache.org> wrote:
>
> > Dan,
> >
> > Thanks for asking about these dependencies. The attached image did not
> come
> > through to the list, but the XML snippet shows the standard test
> > dependencies. These dependencies are applied to all modules by design, to
> > avoid unnecessary repetition in child modules.
> >
> > Regards,
> > David Handermann
> >
> > On Thu, Sep 29, 2022 at 4:06 PM Dan S  wrote:
> >
> > > When looking in the top level pom.xml in IntelliJ I see
> > >
> > > [image: image.png]
> > >
> > >
> > > The duplicate dependencies are:
> > > 
> > > org.junit.jupiter
> > > junit-jupiter-api
> > > test
> > > 
> > > 
> > > org.junit.jupiter
> > > junit-jupiter-engine
> > > test
> > > 
> > > 
> > > org.mockito
> > > mockito-core
> > > test
> > > 
> > > 
> > > org.slf4j
> > > slf4j-simple
> > > test
> > > 
> > > 
> > > org.codehaus.groovy
> > > groovy-test
> > > test
> > > 
> > >
> > > I assume these are oversites. Is this something a ticket should be made
> > > for to fix?
> > >
> > >
> > >
> > >
> >
>

Re: Duplicated dependencies

[Dan S]

Sorry about that. I did not realize I could not include an image. Here is a
text version:

Warning:(624, 10) Dependency is duplicated in file(s):
nifi-zendesk-processors
Warning:(629, 10) Dependency is duplicated in file(s):
nifi-zendesk-processors
Warning:(644, 10) Dependency is duplicated in file(s):
minifi-c2-provider-cache, minifi-c2-provider-delegating,
minifi-c2-provider-nifi-rest, minifi-c2-provider-util,
nifi-azure-reporting-task, nifi-pgp-processors, nifi-pgp-service,
nifi-registry-framework, nifi-registry-jetty,
nifi-registry-revision-spring-jdbc, nifi-registry-aws-extensions,
nifi-registry-ranger-plugin, and nifi-registry-toolkit-persistence
Warning:(654, 10) Dependency is duplicated in file(s):
nifi-system-test-suite
Warning:(659, 10) Dependency is duplicated in file(s):
nifi-registry-framework, nifi-registry-jetty, nifi-registry-properties,
nifi-registry-security-utils, and nifi-registry-web-api

On Thu, Sep 29, 2022 at 5:16 PM David Handermann <
exceptionfact...@apache.org> wrote:

> Dan,
>
> Thanks for asking about these dependencies. The attached image did not come
> through to the list, but the XML snippet shows the standard test
> dependencies. These dependencies are applied to all modules by design, to
> avoid unnecessary repetition in child modules.
>
> Regards,
> David Handermann
>
> On Thu, Sep 29, 2022 at 4:06 PM Dan S  wrote:
>
> > When looking in the top level pom.xml in IntelliJ I see
> >
> > [image: image.png]
> >
> >
> > The duplicate dependencies are:
> > 
> > org.junit.jupiter
> > junit-jupiter-api
> > test
> > 
> > 
> > org.junit.jupiter
> > junit-jupiter-engine
> > test
> > 
> > 
> > org.mockito
> > mockito-core
> > test
> > 
> > 
> > org.slf4j
> > slf4j-simple
> > test
> > 
> > 
> > org.codehaus.groovy
> > groovy-test
> > test
> > 
> >
> > I assume these are oversites. Is this something a ticket should be made
> > for to fix?
> >
> >
> >
> >
>

Re: Duplicated dependencies

[David Handermann]

Dan,

Thanks for asking about these dependencies. The attached image did not come
through to the list, but the XML snippet shows the standard test
dependencies. These dependencies are applied to all modules by design, to
avoid unnecessary repetition in child modules.

Regards,
David Handermann

On Thu, Sep 29, 2022 at 4:06 PM Dan S  wrote:

> When looking in the top level pom.xml in IntelliJ I see
>
> [image: image.png]
>
>
> The duplicate dependencies are:
> 
> org.junit.jupiter
> junit-jupiter-api
> test
> 
> 
> org.junit.jupiter
> junit-jupiter-engine
> test
> 
> 
> org.mockito
> mockito-core
> test
> 
> 
> org.slf4j
> slf4j-simple
> test
> 
> 
> org.codehaus.groovy
> groovy-test
> test
> 
>
> I assume these are oversites. Is this something a ticket should be made
> for to fix?
>
>
>
>

Duplicated dependencies

[Dan S]

When looking in the top level pom.xml in IntelliJ I see

[image: image.png]


The duplicate dependencies are:

org.junit.jupiter
junit-jupiter-api
test


org.junit.jupiter
junit-jupiter-engine
test


org.mockito
mockito-core
test


org.slf4j
slf4j-simple
test


org.codehaus.groovy
groovy-test
test


I assume these are oversites. Is this something a ticket should be made for
to fix?

[VOTE] Release Apache NiFi 1.18.0 (RC3)

[Joe Witt]

Hello,

I am pleased to be calling this vote for the source release of Apache
NiFi 1.18.0.

The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1213

The source being voted upon and the convenience binaries can be found at:
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.18.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.18.0-RC3
The Git commit ID is 5bc64c812b2c76ee2879d8081ceadf62d5e3c702
https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=5bc64c812b2c76ee2879d8081ceadf62d5e3c702

Checksums of nifi-1.18.0-source-release.zip:
SHA256: bd1b675f17dbf712089a79f7bc043eae2df63bcc2e08b2012a6431641037679f
SHA512: 
cea43af57089128ff65bb53e76b2fdfa8dec7397e2bf45d41e35b758b731355075839b9c018ee6284cb15e293b105e248d88748148960ad80ae387824139f52b

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

171 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12352150

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.18.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.18.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...

Re: Git questions for supplying a contribution

[Dan S]

So I forked from repo in Github, cloned from the fork and then I ran
git remote add upstream https://github.com/apache/nifi.git

When I run git remote -v I get

> origin g...@github.com:dan-s1/nifi.git (fetch)
> origin g...@github.com:dan-s1/nifi.git (push)
> upstream https://github.com/apache/nifi.git (fetch)
> upstream https://github.com/apache/nifi.git (push)


Based on the instructions shouldn't I only have

> origin g...@github.com:dan-s1/nifi.git (fetch)
> origin g...@github.com:dan-s1/nifi.git (push)
> upstream https://github.com/apache/nifi.git (fetch)


On Thu, Sep 29, 2022 at 12:07 PM Bryan Bende  wrote:

> You would need to do the "Clone from Fork" step, having first forked
> the repo in Github.
>
> Then your "origin" would be your fork, and you can push anything you
> want to your fork.
>
> You won't have permissions to push anything to the apache repo with
> your current setup.
>
> On Thu, Sep 29, 2022 at 11:54 AM Joe Witt  wrote:
> >
> > Dan
> >
> > You can think of 'upstream' as your 'origin'.
> >
> > You want to add your mirror in there.  You'd submit your code change
> > in a branch to your fork/mirror.  And from that you'd request/submit a
> > pull request to NiFi.  This is important because you wont be able to
> > commit to the apache/nifi codebase for now (but if you become a
> > committer you can - still though we all use the model I mention).
> >
> > Thanks
> >
> > On Thu, Sep 29, 2022 at 8:36 AM Dan S  wrote:
> > >
> > > Based on ContributorGuide-Cloneacopyoftherepository
> > > <
> https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide#ContributorGuide-Cloneacopyoftherepository
> >I
> > > had initially run
> > > git clone https://github.com/apache/nifi.git and then I believe in
> error I
> > > also ran
> > > git remote add upstream https://github.com/apache/nifi.git
> > >
> > > Now when I run git remote -v
> > > I have
> > > origin https://github.com/apache/nifi.git (fetch)
> > > origin https://github.com/apache/nifi.git (push)
> > > upstream https://github.com/apache/nifi.git (fetch)
> > > upstream https://github.com/apache/nifi.git (push)
> > >
> > > The instructions on ContributorGuide-Supplyingacontribution
> > > <
> https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide#ContributorGuide-Supplyingacontribution
> >
> > > for
> > > a PR seem to be when the clone was from a fork (git clone
> > > g...@github.com: > > name>/nifi.git) and from a mirror.
> > >
> > > For my setup can I still run
> > >
> > > git push origin  ?
>

Re: Git questions for supplying a contribution

[Bryan Bende]

You would need to do the "Clone from Fork" step, having first forked
the repo in Github.

Then your "origin" would be your fork, and you can push anything you
want to your fork.

You won't have permissions to push anything to the apache repo with
your current setup.

On Thu, Sep 29, 2022 at 11:54 AM Joe Witt  wrote:
>
> Dan
>
> You can think of 'upstream' as your 'origin'.
>
> You want to add your mirror in there.  You'd submit your code change
> in a branch to your fork/mirror.  And from that you'd request/submit a
> pull request to NiFi.  This is important because you wont be able to
> commit to the apache/nifi codebase for now (but if you become a
> committer you can - still though we all use the model I mention).
>
> Thanks
>
> On Thu, Sep 29, 2022 at 8:36 AM Dan S  wrote:
> >
> > Based on ContributorGuide-Cloneacopyoftherepository
> > I
> > had initially run
> > git clone https://github.com/apache/nifi.git and then I believe in error I
> > also ran
> > git remote add upstream https://github.com/apache/nifi.git
> >
> > Now when I run git remote -v
> > I have
> > origin https://github.com/apache/nifi.git (fetch)
> > origin https://github.com/apache/nifi.git (push)
> > upstream https://github.com/apache/nifi.git (fetch)
> > upstream https://github.com/apache/nifi.git (push)
> >
> > The instructions on ContributorGuide-Supplyingacontribution
> > 
> > for
> > a PR seem to be when the clone was from a fork (git clone
> > g...@github.com: > name>/nifi.git) and from a mirror.
> >
> > For my setup can I still run
> >
> > git push origin  ?

Re: Git questions for supplying a contribution

[Joe Witt]

Dan

You can think of 'upstream' as your 'origin'.

You want to add your mirror in there.  You'd submit your code change
in a branch to your fork/mirror.  And from that you'd request/submit a
pull request to NiFi.  This is important because you wont be able to
commit to the apache/nifi codebase for now (but if you become a
committer you can - still though we all use the model I mention).

Thanks

On Thu, Sep 29, 2022 at 8:36 AM Dan S  wrote:
>
> Based on ContributorGuide-Cloneacopyoftherepository
> I
> had initially run
> git clone https://github.com/apache/nifi.git and then I believe in error I
> also ran
> git remote add upstream https://github.com/apache/nifi.git
>
> Now when I run git remote -v
> I have
> origin https://github.com/apache/nifi.git (fetch)
> origin https://github.com/apache/nifi.git (push)
> upstream https://github.com/apache/nifi.git (fetch)
> upstream https://github.com/apache/nifi.git (push)
>
> The instructions on ContributorGuide-Supplyingacontribution
> 
> for
> a PR seem to be when the clone was from a fork (git clone
> g...@github.com: name>/nifi.git) and from a mirror.
>
> For my setup can I still run
>
> git push origin  ?

Git questions for supplying a contribution

[Dan S]

Based on ContributorGuide-Cloneacopyoftherepository
I
had initially run
git clone https://github.com/apache/nifi.git and then I believe in error I
also ran
git remote add upstream https://github.com/apache/nifi.git

Now when I run git remote -v
I have
origin https://github.com/apache/nifi.git (fetch)
origin https://github.com/apache/nifi.git (push)
upstream https://github.com/apache/nifi.git (fetch)
upstream https://github.com/apache/nifi.git (push)

The instructions on ContributorGuide-Supplyingacontribution

for
a PR seem to be when the clone was from a fork (git clone
g...@github.com:/nifi.git) and from a mirror.

For my setup can I still run

git push origin  ?

Re: Timeouts on Windows builds

[Mike Thomsen]

It might be worth testing Windows against Java 11 or even 17. My guess
is that Java 8 is not getting much support on Windows since OpenJDK 8
seems to be mainly supported by RH/IBM.

On Thu, Sep 29, 2022 at 11:28 AM Joe Witt  wrote:
>
> Yeah definitely not - the CI/CD struggle is real and will always be...
> We just need to keep improving it as things change in those
> environments.
>
> On Thu, Sep 29, 2022 at 8:26 AM Mike Thomsen  wrote:
> >
> > Noticing a lot of timeouts on the Windows builds I've been restarting
> > lately. We don't consider those blockers if the Linux/macOS builds
> > succeed, right?

Re: [VOTE] Release Apache NiFi 1.18.0 (RC2)

[Joe Witt]

This vote is cancelled.  Will get RC3 up soon.

On Thu, Sep 29, 2022 at 7:32 AM Zoltán Kornél Török
 wrote:
>
> Hi all,
> -1 (non-binding)
>
> Build Nifi with several profiles, some of them is not active by default and
> after starting nifi, I got the following error message during startup:
>
> Bootstrap Config File:
> /Users/ztorok/repositories/nifi/nifi-assembly/target/nifi-1.18.0/conf/bootstrap.conf
>
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/commons/lang3/StringUtils
> at 
> org.apache.nifi.bootstrap.util.SecureNiFiConfigUtil.isHttpsSecurityConfiguredWithEmptyPasswords(SecureNiFiConfigUtil.java:75)
> at 
> org.apache.nifi.bootstrap.util.SecureNiFiConfigUtil.configureSecureNiFiProperties(SecureNiFiConfigUtil.java:108)
> at org.apache.nifi.bootstrap.RunNiFi.start(RunNiFi.java:1249)
> at org.apache.nifi.bootstrap.RunNiFi.main(RunNiFi.java:291)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.commons.lang3.StringUtils
> at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:419)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:352)
> ... 4 more
>
> Also use Nifi-registry with ranger extension, cause that rest api
> calls throws me the following exception:
>
> 2022-09-28 07:56:21,568 ERROR
> org.springframework.boot.web.servlet.support.ErrorPageFilter:
> Forwarding to error page from request [/access] due to exception
> [javax.ws.rs.core.UriBuilder.uri(Ljava/lang/String;)Ljavax/ws/rs/core/UriBuilder;]
> java.lang.AbstractMethodError:
> javax.ws.rs.core.UriBuilder.uri(Ljava/lang/String;)Ljavax/ws/rs/core/UriBuilder;
> at javax.ws.rs.core.UriBuilder.fromUri(UriBuilder.java:120)
> at 
> org.glassfish.jersey.servlet.ServletContainer.doFilter(ServletContainer.java:534)
> at 
> org.glassfish.jersey.servlet.ServletContainer.doFilter(ServletContainer.java:494)
> at 
> org.glassfish.jersey.servlet.ServletContainer.doFilter(ServletContainer.java:431)
> at 
> org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:193)
> at 
> org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1626)
> at 
> org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:100)
> at 
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117)
> at 
> org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:193)
> at 
> org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1626)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:337)
> at 
> org.apache.nifi.registry.web.security.authorization.ResourceAuthorizationFilter.forwardRequestWithoutAuthorizationCheck(ResourceAuthorizationFilter.java:151)
>
>
> Joe Witt  ezt írta (időpont: 2022. szept. 29., Cs,
> 9:57):
>
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi 1.18.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1212
> >
> > The source being voted upon and the convenience binaries can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.18.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.18.0-RC2
> > The Git commit ID is a2307ff874b45210472c158a96b5f31298e6c4fc
> >
> > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=a2307ff874b45210472c158a96b5f31298e6c4fc
> >
> > Checksums of nifi-1.18.0-source-release.zip:
> > SHA256: cabe503d58b1614c39ab9c20d4bc92a70d9a971d6c35bf6eb04aabb682a00926
> > SHA512:
> > 3cbcdbb5c04023dc701d0a3ea2b186b74af20f94a3748d7d3f990f74fa92e21627d644330053f2912655dc33fae7d1018360e11ca3dc5624dd2ae19084a7956a
> >
> > 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
> >
> > 164 issues were closed/resolved for this release:
> >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12352150
> >
> > Release note highlights can be found here:
> >
> > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.18.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.18.0
> > [ ] +0 no opinion
> > [ ] -1 Do 

Re: Timeouts on Windows builds

[Joe Witt]

Yeah definitely not - the CI/CD struggle is real and will always be...
We just need to keep improving it as things change in those
environments.

On Thu, Sep 29, 2022 at 8:26 AM Mike Thomsen  wrote:
>
> Noticing a lot of timeouts on the Windows builds I've been restarting
> lately. We don't consider those blockers if the Linux/macOS builds
> succeed, right?

Timeouts on Windows builds

[Mike Thomsen]

Noticing a lot of timeouts on the Windows builds I've been restarting
lately. We don't consider those blockers if the Linux/macOS builds
succeed, right?

[CANCEL][VOTE] Release Apache NiFi 1.18.0 (RC2)

[Joe Witt]

On Thu, Sep 29, 2022 at 7:32 AM Zoltán Kornél Török
 wrote:
>
> Hi all,
> -1 (non-binding)
>
> Build Nifi with several profiles, some of them is not active by default and
> after starting nifi, I got the following error message during startup:
>
> Bootstrap Config File:
> /Users/ztorok/repositories/nifi/nifi-assembly/target/nifi-1.18.0/conf/bootstrap.conf
>
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/commons/lang3/StringUtils
> at 
> org.apache.nifi.bootstrap.util.SecureNiFiConfigUtil.isHttpsSecurityConfiguredWithEmptyPasswords(SecureNiFiConfigUtil.java:75)
> at 
> org.apache.nifi.bootstrap.util.SecureNiFiConfigUtil.configureSecureNiFiProperties(SecureNiFiConfigUtil.java:108)
> at org.apache.nifi.bootstrap.RunNiFi.start(RunNiFi.java:1249)
> at org.apache.nifi.bootstrap.RunNiFi.main(RunNiFi.java:291)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.commons.lang3.StringUtils
> at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:419)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:352)
> ... 4 more
>
> Also use Nifi-registry with ranger extension, cause that rest api
> calls throws me the following exception:
>
> 2022-09-28 07:56:21,568 ERROR
> org.springframework.boot.web.servlet.support.ErrorPageFilter:
> Forwarding to error page from request [/access] due to exception
> [javax.ws.rs.core.UriBuilder.uri(Ljava/lang/String;)Ljavax/ws/rs/core/UriBuilder;]
> java.lang.AbstractMethodError:
> javax.ws.rs.core.UriBuilder.uri(Ljava/lang/String;)Ljavax/ws/rs/core/UriBuilder;
> at javax.ws.rs.core.UriBuilder.fromUri(UriBuilder.java:120)
> at 
> org.glassfish.jersey.servlet.ServletContainer.doFilter(ServletContainer.java:534)
> at 
> org.glassfish.jersey.servlet.ServletContainer.doFilter(ServletContainer.java:494)
> at 
> org.glassfish.jersey.servlet.ServletContainer.doFilter(ServletContainer.java:431)
> at 
> org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:193)
> at 
> org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1626)
> at 
> org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:100)
> at 
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117)
> at 
> org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:193)
> at 
> org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1626)
> at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:337)
> at 
> org.apache.nifi.registry.web.security.authorization.ResourceAuthorizationFilter.forwardRequestWithoutAuthorizationCheck(ResourceAuthorizationFilter.java:151)
>
>
> Joe Witt  ezt írta (időpont: 2022. szept. 29., Cs,
> 9:57):
>
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi 1.18.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1212
> >
> > The source being voted upon and the convenience binaries can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.18.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.18.0-RC2
> > The Git commit ID is a2307ff874b45210472c158a96b5f31298e6c4fc
> >
> > https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=a2307ff874b45210472c158a96b5f31298e6c4fc
> >
> > Checksums of nifi-1.18.0-source-release.zip:
> > SHA256: cabe503d58b1614c39ab9c20d4bc92a70d9a971d6c35bf6eb04aabb682a00926
> > SHA512:
> > 3cbcdbb5c04023dc701d0a3ea2b186b74af20f94a3748d7d3f990f74fa92e21627d644330053f2912655dc33fae7d1018360e11ca3dc5624dd2ae19084a7956a
> >
> > 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
> >
> > 164 issues were closed/resolved for this release:
> >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12352150
> >
> > Release note highlights can be found here:
> >
> > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.18.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.18.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
>
>
> --
> 

Re: [VOTE] Release Apache NiFi 1.18.0 (RC2)

[Zoltán Kornél Török]

Hi all,
-1 (non-binding)

Build Nifi with several profiles, some of them is not active by default and
after starting nifi, I got the following error message during startup:

Bootstrap Config File:
/Users/ztorok/repositories/nifi/nifi-assembly/target/nifi-1.18.0/conf/bootstrap.conf

Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/commons/lang3/StringUtils
at 
org.apache.nifi.bootstrap.util.SecureNiFiConfigUtil.isHttpsSecurityConfiguredWithEmptyPasswords(SecureNiFiConfigUtil.java:75)
at 
org.apache.nifi.bootstrap.util.SecureNiFiConfigUtil.configureSecureNiFiProperties(SecureNiFiConfigUtil.java:108)
at org.apache.nifi.bootstrap.RunNiFi.start(RunNiFi.java:1249)
at org.apache.nifi.bootstrap.RunNiFi.main(RunNiFi.java:291)
Caused by: java.lang.ClassNotFoundException:
org.apache.commons.lang3.StringUtils
at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
at java.lang.ClassLoader.loadClass(ClassLoader.java:419)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
at java.lang.ClassLoader.loadClass(ClassLoader.java:352)
... 4 more

Also use Nifi-registry with ranger extension, cause that rest api
calls throws me the following exception:

2022-09-28 07:56:21,568 ERROR
org.springframework.boot.web.servlet.support.ErrorPageFilter:
Forwarding to error page from request [/access] due to exception
[javax.ws.rs.core.UriBuilder.uri(Ljava/lang/String;)Ljavax/ws/rs/core/UriBuilder;]
java.lang.AbstractMethodError:
javax.ws.rs.core.UriBuilder.uri(Ljava/lang/String;)Ljavax/ws/rs/core/UriBuilder;
at javax.ws.rs.core.UriBuilder.fromUri(UriBuilder.java:120)
at 
org.glassfish.jersey.servlet.ServletContainer.doFilter(ServletContainer.java:534)
at 
org.glassfish.jersey.servlet.ServletContainer.doFilter(ServletContainer.java:494)
at 
org.glassfish.jersey.servlet.ServletContainer.doFilter(ServletContainer.java:431)
at 
org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:193)
at 
org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1626)
at 
org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:100)
at 
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117)
at 
org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:193)
at 
org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1626)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:337)
at 
org.apache.nifi.registry.web.security.authorization.ResourceAuthorizationFilter.forwardRequestWithoutAuthorizationCheck(ResourceAuthorizationFilter.java:151)


Joe Witt  ezt írta (időpont: 2022. szept. 29., Cs,
9:57):

> Hello,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi 1.18.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1212
>
> The source being voted upon and the convenience binaries can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.18.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.18.0-RC2
> The Git commit ID is a2307ff874b45210472c158a96b5f31298e6c4fc
>
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=a2307ff874b45210472c158a96b5f31298e6c4fc
>
> Checksums of nifi-1.18.0-source-release.zip:
> SHA256: cabe503d58b1614c39ab9c20d4bc92a70d9a971d6c35bf6eb04aabb682a00926
> SHA512:
> 3cbcdbb5c04023dc701d0a3ea2b186b74af20f94a3748d7d3f990f74fa92e21627d644330053f2912655dc33fae7d1018360e11ca3dc5624dd2ae19084a7956a
>
> 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
>
> 164 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12352150
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.18.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.18.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>


-- 
Üdvözlettel,
Török Zoltán Kornél
06-30-509-0541

[VOTE] Release Apache NiFi 1.18.0 (RC2)

[Joe Witt]

Hello,

I am pleased to be calling this vote for the source release of Apache
NiFi 1.18.0.

The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1212

The source being voted upon and the convenience binaries can be found at:
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.18.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.18.0-RC2
The Git commit ID is a2307ff874b45210472c158a96b5f31298e6c4fc
https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=a2307ff874b45210472c158a96b5f31298e6c4fc

Checksums of nifi-1.18.0-source-release.zip:
SHA256: cabe503d58b1614c39ab9c20d4bc92a70d9a971d6c35bf6eb04aabb682a00926
SHA512: 
3cbcdbb5c04023dc701d0a3ea2b186b74af20f94a3748d7d3f990f74fa92e21627d644330053f2912655dc33fae7d1018360e11ca3dc5624dd2ae19084a7956a

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

164 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12352150

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.18.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.18.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...