RE: Reporting task can be set to RUNNING from REST API when invalid
Thanks - I have rebased my branch and pipelines are green now in PR. So the code review would be appreciated. -Original Message- From: Joey Frazee Sent: Thursday, 25 June 2020 18:53 To: dev@nifi.apache.org Subject: Re: Reporting task can be set to RUNNING from REST API when invalid One of those looks like it’s just a transient failure. The other on macOS was a flakey test that was fixed recently. If you want it to show green you can rebase. If you re-run the jobs I’d expect to see the Ubuntu/1.8 pass but the macOS one probably won’t until you rebase your branch. -joey On Jun 25, 2020, 9:39 AM -0500, Vasily Makarov , wrote: > Hi all! > Investigated and resolved bug with https://github.com/apache/nifi/pull/4334 , > but there are build errors it seems not related to PR. Should I try to redo > my PR, or what to do? > Also can someone do the code review if possible. (It is my second PR with > Apache NiFi but seems that I fixed the bug).
Reporting task can be set to RUNNING from REST API when invalid
Hi all! Investigated and resolved bug with https://github.com/apache/nifi/pull/4334 , but there are build errors it seems not related to PR. Should I try to redo my PR, or what to do? Also can someone do the code review if possible. (It is my second PR with Apache NiFi but seems that I fixed the bug).
asciidoctor-maven-plugin error on windows
Hi all! When building NiFi on windows I encounter such an error with asciidoctor-maven-plugin: [INFO] BUILD FAILURE [INFO] [INFO] Total time: 01:22 min (Wall Clock) [INFO] Finished at: 2020-06-11T13:42:20+03:00 [INFO] [ERROR] Failed to execute goal org.asciidoctor:asciidoctor-maven-plugin:1.5.2:process-asciidoc (output-html) on project nifi-docs: Execution output-html of goal org.asciidoctor:asciidoctor-maven-plugin:1.5.2:process-asciidoc failed: (LoadError) no such file to load -- asciidoctor -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :nifi-docs I have temporarily resolved this issue by commenting out these rows in nifi-docs pom.xml: Building with Java 1.8.0_211-b12, but I also have tried with newer versions of Java. Is it a known issue or should I create an issue in Jira?
NiFi module with curator error
Hi all! 1. Which NiFi module can throw such an error? nifi-framework-core? This exception is due that not all zookeeper nodes defined in logs are up and running. 2. 2. Can this connection request to the curator/zookeper be found in java code in some particular line of code? Or is it like in the configuration side? 2020-01-16 08:58:28,767 ERROR [Curator-Framework-0] o.a.c.f.imps.CuratorFrameworkImpl Background retry gave up org.apache.curator.CuratorConnectionLossException: KeeperErrorCode = ConnectionLoss at org.apache.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:972) at org.apache.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:943) at org.apache.curator.framework.imps.CuratorFrameworkImpl.access$300(CuratorFrameworkImpl.java:66) at org.apache.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:346) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) (I'm working on https://jira.apache.org/jira/browse/NIFI-7035 - right now my idea is to implement custom turbo filter in logbase to limit this spam of CuratorFrameworkImpl logs. Any help would be appreciated)
Jira contributor access - feitgraph
Hi! I would like to join Apache NiFi open source community and to participate in open source development. My login in Apache Jira is: feitgraph I would like to start with these two tasks: https://jira.apache.org/jira/browse/NIFI-7057 https://jira.apache.org/jira/browse/NIFI-7035 Thanks in advance! Vasiliy Makarov.
