Re: [VOTE] Release Apache NiFi 1.7.1

[Andy LoPresto]

Thanks for catching that Drew. I missed cherry picking the commit into the 
release branch. I don’t think it rises to the level of canceling this release, 
but I will note in the release notes that the ticket is not included and add 
extra notes to the migration guidance. 

Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Jul 13, 2018, at 13:53, Andrew Lim  wrote:
> 
> +1 (non-binding)
> 
> -Ran full clean install on OS X (10.11.6)
> -Tested integration with NiFi Registry (0.2.0)
> -Ran some basic flows; working as expected.
> -Reviewed documentation.  Noticed that the doc added for wildcard 
> certificates was included in master but not 1.7.1  [1]
> 
> Drew
> 
> [1] https://issues.apache.org/jira/browse/NIFI-5339
> 
>> On Jul 12, 2018, at 4:59 PM, Andy LoPresto  wrote:
>> 
>> Hello,
>> 
>> I am pleased to be calling this vote for the source release of Apache NiFi 
>> nifi-1.7.1.
>> 
>> The source zip, including signatures, digests, etc. can be found at:
>> https://repository.apache.org/content/repositories/orgapachenifi-1131
>> 
>> The Git tag is nifi-1.7.1-RC1
>> The Git commit ID is 241e5411a24435ca2c39ab7bea1c5eb9ed195cb3
>> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=241e5411a24435ca2c39ab7bea1c5eb9ed195cb3
>> 
>> Checksums of nifi-1.7.1-source-release.zip:
>> SHA1: 92428e219f8792b886a2826119d3f70c98de52fe
>> SHA256: e951a0a2c6b7f8e742b8ab126532ab2e02876ba8c1db34b858fb72718a9fa0e6
>> SHA512: 
>> a37add06c3c4f2ae5294c9f7668e2e837d6b92095d8e349d18cb13a1748c0e052632415e0fda148f55b61f6774bcdd487ee3d8b8125fe4d2345791da1fc7d8d9
>> 
>> Release artifacts are signed with the following key:
>> https://people.apache.org/keys/committer/alopresto.asc
>> 
>> KEYS file available here:
>> https://dist.apache.org/repos/dist/release/nifi/KEYS
>> 
>> 13 issues were closed/resolved for this release:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12343647
>> 
>> Release note highlights can be found here:
>> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.7.1
>> 
>> The vote will be open for 96 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.7.1
>> [ ] +0 no opinion
>> [ ] -1 Do not release this package because…
>> 
>> Andy LoPresto
>> alopre...@apache.org
>> alopresto.apa...@gmail.com
>> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>> 
> 

Re: [VOTE] Release Apache NiFi 1.7.1

[Andrew Lim]

+1 (non-binding)

-Ran full clean install on OS X (10.11.6)
-Tested integration with NiFi Registry (0.2.0)
-Ran some basic flows; working as expected.
-Reviewed documentation.  Noticed that the doc added for wildcard certificates 
was included in master but not 1.7.1  [1]

Drew

[1] https://issues.apache.org/jira/browse/NIFI-5339

> On Jul 12, 2018, at 4:59 PM, Andy LoPresto  wrote:
> 
> Hello,
> 
> I am pleased to be calling this vote for the source release of Apache NiFi 
> nifi-1.7.1.
> 
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1131
> 
> The Git tag is nifi-1.7.1-RC1
> The Git commit ID is 241e5411a24435ca2c39ab7bea1c5eb9ed195cb3
> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=241e5411a24435ca2c39ab7bea1c5eb9ed195cb3
> 
> Checksums of nifi-1.7.1-source-release.zip:
> SHA1: 92428e219f8792b886a2826119d3f70c98de52fe
> SHA256: e951a0a2c6b7f8e742b8ab126532ab2e02876ba8c1db34b858fb72718a9fa0e6
> SHA512: 
> a37add06c3c4f2ae5294c9f7668e2e837d6b92095d8e349d18cb13a1748c0e052632415e0fda148f55b61f6774bcdd487ee3d8b8125fe4d2345791da1fc7d8d9
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/alopresto.asc
> 
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> 13 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12343647
> 
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.7.1
> 
> The vote will be open for 96 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.7.1
> [ ] +0 no opinion
> [ ] -1 Do not release this package because…
> 
> Andy LoPresto
> alopre...@apache.org
> alopresto.apa...@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> 

Re: [VOTE] Release Apache NiFi 1.7.1

[Matt Gilman]

+1 (binding)

Verified signatures, hashes, build, etc.

Ran into one minor thing that probably warrants a note in the migration
guide. The certificates that I used in my cluster previously no longer
work. It appears the issue is my fault because the certificates did not
have the hostname properly specified in the subjectAlternativeNames. Once I
issued new certificates with these entries all was good. Since this check
is now more strict, we should probably call this out in case others happen
to be using certificates like I was.

Thanks for RMing Andy!

Matt

On Fri, Jul 13, 2018 at 3:44 PM, Mark Payne  wrote:

> +1 (binding).
>
> Verified checksums and hashes.
> Verified full build with contrib-check.
> Verified that the app starts and provides the basic functionalities.
> Verified that wildcard certificates now work in clustered mode.
> Verified that the recursively referenced Controller Services now behave as
> expected, not throwing StackOverflowException.
>
> Many thanks for handling the RM duties, Andy!
>
> Thanks
> -Mark
>
>
> On Jul 13, 2018, at 2:24 PM, Andy LoPresto  lopre...@apache.org>> wrote:
>
> Peter,
>
> Thanks for validating. The tag was pushed to the official repository [1]
> but not mirrored to github yet. For the official release, it will be there.
>
> [1] https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=tag;h=
> 411983dbafaaae8d76a2d7a4ae4b8d1177fae1eb
>
> Andy LoPresto
> alopre...@apache.org
> alopresto.apa...@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> On Jul 13, 2018, at 9:55 AM, James Wing mailto:jvwin
> g...@gmail.com>> wrote:
>
> +1 (binding).  Ran through the release helper, checked license, notice,
> readme files, and tested the resulting binary.
>
> Thanks for putting this together, Andy.
>
> On Thu, Jul 12, 2018 at 2:00 PM Andy LoPresto  > wrote:
>
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> nifi-1.7.1.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1131
>
> The Git tag is nifi-1.7.1-RC1
> The Git commit ID is 241e5411a24435ca2c39ab7bea1c5eb9ed195cb3
>
> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> 241e5411a24435ca2c39ab7bea1c5eb9ed195cb3
>
> Checksums of nifi-1.7.1-source-release.zip:
> SHA1: 92428e219f8792b886a2826119d3f70c98de52fe
> SHA256: e951a0a2c6b7f8e742b8ab126532ab2e02876ba8c1db34b858fb72718a9fa0e6
> SHA512:
> a37add06c3c4f2ae5294c9f7668e2e837d6b92095d8e349d18cb13a1748c
> 0e052632415e0fda148f55b61f6774bcdd487ee3d8b8125fe4d2345791da1fc7d8d9
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/alopresto.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 13 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12316020=12343647
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFI/
> Release+Notes#ReleaseNotes-Version1.7.1
>
> The vote will be open for 96 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.7.1
> [ ] +0 no opinion
> [ ] -1 Do not release this package because…
>
> Andy LoPresto
> alopre...@apache.org
> *alopresto.apa...@gmail.com <
> alopresto.apa...@gmail.com>*
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
>
>

Re: [VOTE] Release Apache NiFi 1.7.1

[Mark Payne]

+1 (binding).

Verified checksums and hashes.
Verified full build with contrib-check.
Verified that the app starts and provides the basic functionalities.
Verified that wildcard certificates now work in clustered mode.
Verified that the recursively referenced Controller Services now behave as 
expected, not throwing StackOverflowException.

Many thanks for handling the RM duties, Andy!

Thanks
-Mark


On Jul 13, 2018, at 2:24 PM, Andy LoPresto 
mailto:alopre...@apache.org>> wrote:

Peter,

Thanks for validating. The tag was pushed to the official repository [1] but 
not mirrored to github yet. For the official release, it will be there.

[1] 
https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=tag;h=411983dbafaaae8d76a2d7a4ae4b8d1177fae1eb

Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

On Jul 13, 2018, at 9:55 AM, James Wing 
mailto:jvw...@gmail.com>> wrote:

+1 (binding).  Ran through the release helper, checked license, notice,
readme files, and tested the resulting binary.

Thanks for putting this together, Andy.

On Thu, Jul 12, 2018 at 2:00 PM Andy LoPresto 
mailto:alopre...@apache.org>> wrote:

Hello,

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

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

The Git tag is nifi-1.7.1-RC1
The Git commit ID is 241e5411a24435ca2c39ab7bea1c5eb9ed195cb3

https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=241e5411a24435ca2c39ab7bea1c5eb9ed195cb3

Checksums of nifi-1.7.1-source-release.zip:
SHA1: 92428e219f8792b886a2826119d3f70c98de52fe
SHA256: e951a0a2c6b7f8e742b8ab126532ab2e02876ba8c1db34b858fb72718a9fa0e6
SHA512:
a37add06c3c4f2ae5294c9f7668e2e837d6b92095d8e349d18cb13a1748c0e052632415e0fda148f55b61f6774bcdd487ee3d8b8125fe4d2345791da1fc7d8d9

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/alopresto.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/nifi/KEYS

13 issues were closed/resolved for this release:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12343647

Release note highlights can be found here:

https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.7.1

The vote will be open for 96 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.7.1
[ ] +0 no opinion
[ ] -1 Do not release this package because…

Andy LoPresto
alopre...@apache.org
*alopresto.apa...@gmail.com 
mailto:alopresto.apa...@gmail.com>>*
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

[DISCUSS] NiFi shared file system

[Mark Bean]

I'd like to start a discussion on making NiFi Clustering more robust. As it
is, a Cluster is very beneficial from a management standpoint. A change
only needs to be made in one place - any place - and it is replicated
across the cluster. However, from a data perspective, the same flexibility
is not available. Data is node-specific and a flowfile will only ever exist
on a single node. Start thinking single point of failure. It would be
desirable if data could be shuffled over to the same point in the flow on
another (less busy) node to complete processing.

There are many factors to consider such as the time it would take to
transfer flowfiles to another node versus waiting for a transient spike in
load to return to normal levels. However, consider the other extreme, where
a node crashes or for some reason is removed from the cluster (but the file
system is still available). The data could be recovered from the
problematic node and processed by surviving nodes. This also allows for
flexibility to dynamically spin up _and down_ additional NiFi instances
on-demand while not having to wait to bleed off data when removing a node
from the cluster.

Fundamentally, this comes down to some form of shared file system across
the Cluster.

Admittedly, there are very complex issues involved not the least of which
is proper synchronization. Yet the concept could provide huge benefits
especially in terms of load balancing across the Cluster.

-Mark

Re: [VOTE] Release Apache NiFi 1.7.1

[Andy LoPresto]

Peter,

Thanks for validating. The tag was pushed to the official repository [1] but 
not mirrored to github yet. For the official release, it will be there.

[1] 
https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=tag;h=411983dbafaaae8d76a2d7a4ae4b8d1177fae1eb
 


Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Jul 13, 2018, at 9:55 AM, James Wing  wrote:
> 
> +1 (binding).  Ran through the release helper, checked license, notice,
> readme files, and tested the resulting binary.
> 
> Thanks for putting this together, Andy.
> 
> On Thu, Jul 12, 2018 at 2:00 PM Andy LoPresto  > wrote:
> 
>> Hello,
>> 
>> I am pleased to be calling this vote for the source release of Apache NiFi
>> nifi-1.7.1.
>> 
>> The source zip, including signatures, digests, etc. can be found at:
>> https://repository.apache.org/content/repositories/orgapachenifi-1131
>> 
>> The Git tag is nifi-1.7.1-RC1
>> The Git commit ID is 241e5411a24435ca2c39ab7bea1c5eb9ed195cb3
>> 
>> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=241e5411a24435ca2c39ab7bea1c5eb9ed195cb3
>> 
>> Checksums of nifi-1.7.1-source-release.zip:
>> SHA1: 92428e219f8792b886a2826119d3f70c98de52fe
>> SHA256: e951a0a2c6b7f8e742b8ab126532ab2e02876ba8c1db34b858fb72718a9fa0e6
>> SHA512:
>> a37add06c3c4f2ae5294c9f7668e2e837d6b92095d8e349d18cb13a1748c0e052632415e0fda148f55b61f6774bcdd487ee3d8b8125fe4d2345791da1fc7d8d9
>> 
>> Release artifacts are signed with the following key:
>> https://people.apache.org/keys/committer/alopresto.asc
>> 
>> KEYS file available here:
>> https://dist.apache.org/repos/dist/release/nifi/KEYS
>> 
>> 13 issues were closed/resolved for this release:
>> 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12343647
>> 
>> Release note highlights can be found here:
>> 
>> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.7.1
>> 
>> The vote will be open for 96 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.7.1
>> [ ] +0 no opinion
>> [ ] -1 Do not release this package because…
>> 
>> Andy LoPresto
>> alopre...@apache.org
>> *alopresto.apa...@gmail.com  
>> mailto:alopresto.apa...@gmail.com>>*
>> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [VOTE] Release Apache NiFi 1.7.1

[James Wing]

+1 (binding).  Ran through the release helper, checked license, notice,
readme files, and tested the resulting binary.

Thanks for putting this together, Andy.

On Thu, Jul 12, 2018 at 2:00 PM Andy LoPresto  wrote:

> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> nifi-1.7.1.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1131
>
> The Git tag is nifi-1.7.1-RC1
> The Git commit ID is 241e5411a24435ca2c39ab7bea1c5eb9ed195cb3
>
> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=241e5411a24435ca2c39ab7bea1c5eb9ed195cb3
>
> Checksums of nifi-1.7.1-source-release.zip:
> SHA1: 92428e219f8792b886a2826119d3f70c98de52fe
> SHA256: e951a0a2c6b7f8e742b8ab126532ab2e02876ba8c1db34b858fb72718a9fa0e6
> SHA512:
> a37add06c3c4f2ae5294c9f7668e2e837d6b92095d8e349d18cb13a1748c0e052632415e0fda148f55b61f6774bcdd487ee3d8b8125fe4d2345791da1fc7d8d9
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/alopresto.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 13 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12343647
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.7.1
>
> The vote will be open for 96 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.7.1
> [ ] +0 no opinion
> [ ] -1 Do not release this package because…
>
> Andy LoPresto
> alopre...@apache.org
> *alopresto.apa...@gmail.com *
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
>

RE: [EXT] Re: Dark mode

[Peter Wicks (pwicks)]

I did something similar back in 1.2.0 using CSS overrides and a chrome plugin : 
https://userstyles.org/styles/142978/dark-nifi-1-2-0.


-Original Message-
From: Brandon DeVries [mailto:b...@jhu.edu] 
Sent: Friday, July 13, 2018 9:42 AM
To: dev@nifi.apache.org
Subject: [EXT] Re: Dark mode

I think there are a lot of people that would be a big +1 on this.  Maybe
even more so if it was abstracted so there could be multiple / custom
"themes" (e.g. dark, classic, high contrast / 508 compliant...).

Brandon

On Fri, Jul 13, 2018 at 7:29 AM Joe Witt  wrote:

> Rich
>
> This could certainly be an interesting option.  Perhaps file a JIRA
> with some details on where you're at in your PR and post that when
> ready.  Identify things you think might be remaining and such..
>
> Thanks
>
> On Fri, Jul 13, 2018 at 7:25 AM, Rich M  wrote:
> > Hi
> >
> > Going through some NiFi bits and pieces while I'm between projects;
> > I've got a half-baked dark mode kicking around, is there any interest
> > in me pushing this to a remote branch somewhere? There's some iframes
> > in dialogs missing styling, it probably wants someone more familiar
> > with Angular to look at it and a couple of places the styling isn't
> > applied to so it'd need a little work to even consider merging.
> >
> > https://i.imgur.com/lSofSq5.jpg
> >
> > Rich
>

Re: Dark mode

[Brandon DeVries]

I think there are a lot of people that would be a big +1 on this.  Maybe
even more so if it was abstracted so there could be multiple / custom
"themes" (e.g. dark, classic, high contrast / 508 compliant...).

Brandon

On Fri, Jul 13, 2018 at 7:29 AM Joe Witt  wrote:

> Rich
>
> This could certainly be an interesting option.  Perhaps file a JIRA
> with some details on where you're at in your PR and post that when
> ready.  Identify things you think might be remaining and such..
>
> Thanks
>
> On Fri, Jul 13, 2018 at 7:25 AM, Rich M  wrote:
> > Hi
> >
> > Going through some NiFi bits and pieces while I'm between projects;
> > I've got a half-baked dark mode kicking around, is there any interest
> > in me pushing this to a remote branch somewhere? There's some iframes
> > in dialogs missing styling, it probably wants someone more familiar
> > with Angular to look at it and a couple of places the styling isn't
> > applied to so it'd need a little work to even consider merging.
> >
> > https://i.imgur.com/lSofSq5.jpg
> >
> > Rich
>

Re: [VOTE] Release Apache NiFi 1.7.1

[Joe Witt]

+1 (binding)

verified full build with contrib check and all tests (linux and osx),
sig, hashes, version, L, and last couple of commits included.

Noted Peter's finding of the RC tag not being present but that is ok
since the noted commit is.  The real release tag will be pushed so
that is ok.

Thanks again Andy - i know the RC process takes a lot of time!

Joe

On Fri, Jul 13, 2018 at 8:41 AM, Peter Wilcsinszky
 wrote:
> +1
>
> However I can't see the release tag "nifi-1.7.1-RC1".
>
> curl -s https://github.com/apache/nifi/tree/nifi-1.7.1-RC1 -w
> '%{http_code}\n' -o /dev/null
> 404
>
> vs:
>
> curl -s https://github.com/apache/nifi/tree/nifi-1.7.0-RC1 -w
> '%{http_code}\n' -o /dev/null
> 200
>
> Is it really missing or will be tagged along with the final release?
>
> Other than that everything looks good:
>  - Verified the commit.
>  - Checked using diff, that the release commit matches the release
> artifact's content.
>  - Checked and verified signature and checksums.
>  - Checked git log against release 1.7.0 contains the issues listed.
>  - Built and started NiFi from the release artifact without issues.
>
>
> On Thu, Jul 12, 2018 at 11:00 PM Andy LoPresto  wrote:
>
>> Hello,
>>
>> I am pleased to be calling this vote for the source release of Apache NiFi
>> nifi-1.7.1.
>>
>> The source zip, including signatures, digests, etc. can be found at:
>> https://repository.apache.org/content/repositories/orgapachenifi-1131
>>
>> The Git tag is nifi-1.7.1-RC1
>> The Git commit ID is 241e5411a24435ca2c39ab7bea1c5eb9ed195cb3
>>
>> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=241e5411a24435ca2c39ab7bea1c5eb9ed195cb3
>>
>> Checksums of nifi-1.7.1-source-release.zip:
>> SHA1: 92428e219f8792b886a2826119d3f70c98de52fe
>> SHA256: e951a0a2c6b7f8e742b8ab126532ab2e02876ba8c1db34b858fb72718a9fa0e6
>> SHA512:
>> a37add06c3c4f2ae5294c9f7668e2e837d6b92095d8e349d18cb13a1748c0e052632415e0fda148f55b61f6774bcdd487ee3d8b8125fe4d2345791da1fc7d8d9
>>
>> Release artifacts are signed with the following key:
>> https://people.apache.org/keys/committer/alopresto.asc
>>
>> KEYS file available here:
>> https://dist.apache.org/repos/dist/release/nifi/KEYS
>>
>> 13 issues were closed/resolved for this release:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12343647
>>
>> Release note highlights can be found here:
>>
>> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.7.1
>>
>> The vote will be open for 96 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.7.1
>> [ ] +0 no opinion
>> [ ] -1 Do not release this package because…
>>
>> Andy LoPresto
>> alopre...@apache.org
>> *alopresto.apa...@gmail.com *
>> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>>
>>

Re: [VOTE] Release Apache NiFi 1.7.1

[Peter Wilcsinszky]

+1

However I can't see the release tag "nifi-1.7.1-RC1".

curl -s https://github.com/apache/nifi/tree/nifi-1.7.1-RC1 -w
'%{http_code}\n' -o /dev/null
404

vs:

curl -s https://github.com/apache/nifi/tree/nifi-1.7.0-RC1 -w
'%{http_code}\n' -o /dev/null
200

Is it really missing or will be tagged along with the final release?

Other than that everything looks good:
 - Verified the commit.
 - Checked using diff, that the release commit matches the release
artifact's content.
 - Checked and verified signature and checksums.
 - Checked git log against release 1.7.0 contains the issues listed.
 - Built and started NiFi from the release artifact without issues.


On Thu, Jul 12, 2018 at 11:00 PM Andy LoPresto  wrote:

> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> nifi-1.7.1.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1131
>
> The Git tag is nifi-1.7.1-RC1
> The Git commit ID is 241e5411a24435ca2c39ab7bea1c5eb9ed195cb3
>
> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=241e5411a24435ca2c39ab7bea1c5eb9ed195cb3
>
> Checksums of nifi-1.7.1-source-release.zip:
> SHA1: 92428e219f8792b886a2826119d3f70c98de52fe
> SHA256: e951a0a2c6b7f8e742b8ab126532ab2e02876ba8c1db34b858fb72718a9fa0e6
> SHA512:
> a37add06c3c4f2ae5294c9f7668e2e837d6b92095d8e349d18cb13a1748c0e052632415e0fda148f55b61f6774bcdd487ee3d8b8125fe4d2345791da1fc7d8d9
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/alopresto.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 13 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12343647
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.7.1
>
> The vote will be open for 96 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.7.1
> [ ] +0 no opinion
> [ ] -1 Do not release this package because…
>
> Andy LoPresto
> alopre...@apache.org
> *alopresto.apa...@gmail.com *
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
>

Re: Dark mode

[Joe Witt]

Rich

This could certainly be an interesting option.  Perhaps file a JIRA
with some details on where you're at in your PR and post that when
ready.  Identify things you think might be remaining and such..

Thanks

On Fri, Jul 13, 2018 at 7:25 AM, Rich M  wrote:
> Hi
>
> Going through some NiFi bits and pieces while I'm between projects;
> I've got a half-baked dark mode kicking around, is there any interest
> in me pushing this to a remote branch somewhere? There's some iframes
> in dialogs missing styling, it probably wants someone more familiar
> with Angular to look at it and a couple of places the styling isn't
> applied to so it'd need a little work to even consider merging.
>
> https://i.imgur.com/lSofSq5.jpg
>
> Rich

Dark mode

[Rich M]

Hi

Going through some NiFi bits and pieces while I'm between projects;
I've got a half-baked dark mode kicking around, is there any interest
in me pushing this to a remote branch somewhere? There's some iframes
in dialogs missing styling, it probably wants someone more familiar
with Angular to look at it and a couple of places the styling isn't
applied to so it'd need a little work to even consider merging.

https://i.imgur.com/lSofSq5.jpg

Rich

the question about nifi cache auto clear default(5 min)

[Xu, Zhi-Chao]

Hi

I found that in/out will be cleared after 5 min. the same as the report an =

error/warn/debug

But  I don't' want it auto clear or I can change the time . I don't' found =

configuration  anywhere.

How should I do ?

Thank you very mach.





Best Regards,

Zhichao.xu