+1 (binding) Release this package as nifi-minifi-cpp-0.0.1
- Ran through the helper
- Ran a couple simple flows
Everything worked as expected.
This is a great step for MiNiFi! Thank you Bin and Aldrin for all your hard
work.
Joe
- - - - - -
Joseph Percivall
linkedin.com/in/Percivall
e:
Tony,
I tend to agree with your view but I was under the impression the proposed
change does not make changes to NiFi itself?
Correct me if I am wrong - maven still feels quite cryptic to me - but my
understanding was that the PR only configures tests to be ran with a
particular variable java
Tony,
In terms of the GMock, this transitive inclusion was detected but based off
versions, as best as I could surmise is now part of Google Test as per
their repo here: https://github.com/google/googlemock. This inclusion is
covered in the LICENSE [1]
We can certainly can and should clean up
+1 (non-binding) Release this package as nifi-minifi-cpp-0.0.1
- Verified signature, hashes, and LICENSE/NOTICE/README
- Built source and ran a simple flow with GetFile -> RPG -> Standalone NiFi
- Environment -- MiNiFi Ubuntu 16.04.1 LTS and Standalone NiFi OSX
I also noticed all of the
Hi Joe, I dont seem to have access to nifi jira to create one. Can it be
given? Or if not, could someone help raising it.
On Tue, Aug 30, 2016, 7:49 AM Joe Percivall wrote:
> - Moving users list to BCC
>
> Hello Gunjan,
>
> This seems like a good potential idea. The
I had a lot of warnings when I built also, lots of unsigned / signed
comparisons, for example.
I'm building on a fairly vanilla Ubuntu 14.04 x64_64 box. I can paste if
people are interested.
On Aug 29, 2016 10:06 PM, "Andy LoPresto" wrote:
> Downloaded, verified the GPG
- Moving users list to BCC
Hello Gunjan,
This seems like a good potential idea. The proper place to submit the
suggestion is through the Apache NiFi Jira[1]. It can more easily be discussed
and worked on there.
[1] https://issues.apache.org/jira/browse/NIFI
Suggestions/ideas from users are
Downloaded, verified the GPG signature and checksums, checked the README,
LICENSE, and NOTICE files. Verified the git commit ID.
Built with make (had to install boost using Homebrew first). I got a couple
warnings & errors during the make process (documented below) — not sure if they
are known
Andre,
I've been reluctant to do a software change for something that is,
debatably an environment issue. If DISPLAY is set, I would think one would
be reasonably assured one had an x server.
On Mon, Aug 29, 2016 at 8:02 PM, Andre wrote:
> Tony,
>
> Yes. That happens when
I agree that the error message definitely needs improvement but I don't think
it's a blocker level issue for an 0.0.1 release.
Joe
- - - - - -
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com
On Tuesday, August 30, 2016 11:34 AM, Tony Kurc wrote:
I'm
All,
Question about the LICENSE file, I didn't see gmock
(thirdparty/yaml-cpp-yaml-cpp-0.5.3/test/gmock-1.7.0) listed in the LICENSE
, is this because it is "bundled" with yaml-cpp?
Tony
On Mon, Aug 29, 2016 at 9:34 PM, Tony Kurc wrote:
> I'm not sure how minor that missing
I'm not sure how minor that missing flow.yml issue is - the error message
when flow.yml isn't there is a bit hard to determine what the error was:
"terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_S_construct null not valid"
On Mon, Aug 29, 2016 at
I apologize, with all the activity I missed a change of vote from -1 to +0
(non-binding). The updated count is below:
7 +1 (binding) votes
8 +1 (non-binding) votes
1 +0 (non-binding) votes
1 -0.9 (non-binding) votes
0 -1 (binding) votes
0 -1 (non-binding) votes
Thanks again to all those who
Hello
The release passes with
7 +1 (binding) votes
8 +1 (non-binding) votes
1 -0.9 (non-binding) votes
0 -1 (binding) votes
1 -1 (non-binding) votes
Thanks to all who helped make this release possible.
Here is the PMC vote thread:
Tony,
Yes. That happens when the JDK is not headless. I submitted a PR that
forces maven to run in headless mode which also solves the issue.
Have you had a chance to check https://github.com/apache/nifi/pull/961 ?
Cheers
On Tue, Aug 30, 2016 at 9:57 AM, Tony Kurc wrote:
>
Andre, on the X11 issue, it can occur if you have the DISPLAY environment
variable set, but no X server.
I reported it a while back with what got me past it:
https://issues.apache.org/jira/browse/NIFI-1154
On Aug 29, 2016 11:00 AM, "Yolanda Davis" wrote:
> Resending
Forgot one minor remark:
If I connect via SSH to my VM and call './minifi.sh stop' when minifi.sh is
already stopped, I get disconnected from the VM and cannot reconnect it
unless I reboot the VM.
I opened a JIRA: https://issues.apache.org/jira/browse/MINIFI-97
2016-08-29 23:45 GMT+02:00 Pierre
+1 (non-binding) release this package as nifi-minifi-cpp-0.0.1
- verified signatures, hashes, and LICENSE/NOTICE/README
- built sources on CentOS 7 and ran a GenerateFlowFile -> RPG -> Standalone
NiFi
Remark:
- in the readme, the requirement "libboost" is "boost" on CentOS 7, I don't
know if it
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
-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
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
+1 (binding) Release this package as nifi-minifi-cpp-0.0.1
- Verified signature, hashes, and LICENSE/NOTICE/README
- Built source and ran a simple flow with GetFile -> RPG -> Standalone NiFi
Minor note, in the README it said a flow.yml was included in the conf
directory, but the conf directory
+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
+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
+1 (non-binding) Release this package as nifi-1.0.0
- Verified checksums, signature, LICENSE/NOTICE/README
- Built source with contrib-check
- Tested standalone and clustered instances
There were two issues that I ran into that are minor and are
user-experience-based. The first issue
+1 (non-binding)
- Verified checksums, signature, and commit hash
- Ran build on OS X with all tests and contrib-check
- Tested recent ExtractHL7Attributes (NIFI-2564) and TransformXml (NIFI-2142)
improvements, and template import/export on an unsecured cluster with external
ZK
On Aug 26,
+1, binding
Hashes check out
Signature looks good
Build looked good and ran on OS X, CentOS, Debian
Sample flows from templates check out and look good.
Only small hangup was none of the TestListenSMTP tests passing in Windows
10 as created but worked with relaxed timeouts. Created a JIRA issue
+1 (binding) Release this package as nifi-1.0.0
- Verified checksums, signature, commit hash, and LICENSE/NOTICE/README
- Performed full build with contrib-check
- Tested a standalone unsecure instance and then used the toolkit to create
a secure cluster
On Mon, Aug 29, 2016 at 11:00 AM, Yolanda
Resending on appropriate thread:
+1 (non-binding)
Ran full test suite, with rat and contrib-check. Verified, readme, notice,
license, commit ID, hashes and checksums. Tested flows and templates in
standalone cluster (on Mac OS).
On Fri, Aug 26, 2016 at 12:25 PM, Joe Percivall <
+1 (non-binding)
Ran full test suite, with rat and contrib-check. Verified, readme, notice,
license, commit ID, hashes and checksums. Tested flows and templates in
standalone cluster (on Mac OS).
On Fri, Aug 26, 2016 at 12:26 PM, Joe Percivall <
joeperciv...@yahoo.com.invalid> wrote:
> Hello
+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
@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 wrote:
> @Joe I don't have the anniversary update yet.
>
> 2016-08-29 13:56 GMT+02:00 Joe Skora
@Joe I don't have the anniversary update yet.
2016-08-29 13:56 GMT+02:00 Joe Skora :
> 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
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
+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 <
joeperciv...@yahoo.com.invalid> wrote:
> Hello Apache NiFi Community,
>
> I am pleased to be calling this vote for the
35 matches
Mail list logo