Re: Azure lib issue in 1.26
Eduardo Yes this was found/fixed today[1] Sorry for the trouble [1] https://issues.apache.org/jira/browse/NIFI-13181 Thanks Joe On Wed, May 8, 2024 at 6:59 PM Eduardo Fontes wrote: > Hi! > > Someone with errors like that em Azure components in Nifi 1.26? > > java.lang.NoSuchMethodError: > 'com.microsoft.aad.msal4j.AbstractApplicationBase$Builder > > com.microsoft.aad.msal4j.ConfidentialClientApplication$Builder.logPii(boolean)' > > I see thar msal lib was updated since 1.25. > > Best regards. > Eduardo Fontes >
Azure lib issue in 1.26
Hi! Someone with errors like that em Azure components in Nifi 1.26? java.lang.NoSuchMethodError: 'com.microsoft.aad.msal4j.AbstractApplicationBase$Builder com.microsoft.aad.msal4j.ConfidentialClientApplication$Builder.logPii(boolean)' I see thar msal lib was updated since 1.25. Best regards. Eduardo Fontes
Modernizing Nifi Archetypes
Hi, I've created https://issues.apache.org/jira/browse/NIFI-13187 to suggest some changes to modernize the Nifi Archetypes. Specifically: Modernize Nifi's Java archetypes using Immutable Map, List utils Provide more readable property and relationship names Provide example of flow file transfer usage Not sure if there are other items to consider to keep them basic but useful to help developers get started. Open to other suggestions [1] - Bob [1] https://github.com/apache/nifi/pull/8783
Re: ...not the most recent version of this FlowFile within this session...
Oh yeah, I do love this behavior of ProcessSession. And thanks for the
tip, it's easy to forget that there are efficiencies to be gained by using
different parts of an API.
-- Mke
On Wed, May 8, 2024 at 11:04 AM Mark Payne wrote:
> Yeah, that was something that kinda flew under the radar. Definitely
> improved the API.
>
> Not really related, but on the note of things you may not realize, with
> that code snippet :)
> If you have access to update the processor mentioned here, you should
> avoid using session.putAttribute many times.
> Under the hood, in order to maintain object immutability it has to create
> a new FlowFile object (and a new HashMap of all attributes!)
> for every call to putAttribute. So if there are 100 attributes that match
> that’s potentially a huge amount of garbage getting created. Instead,
> you could just use:
>
> ```
> final Map attributes = new HashMap<>();
> flowFile.getAttributes().forEach( (key, value) -> {
> if (key.startsWith(“foo”)) {
> attributes.put(“original-“ + key, value);
> }
> }
>
> flowFIle = session.putAllAttributes(flowFile, attributes);
> ```
>
> Thanks
> -Mark
>
>
>
> > On May 8, 2024, at 10:30 AM, Michael Moser wrote:
> >
> > Wow, thanks for this information! Just last week I saw code that
> modified
> > attributes in a stream:
> >
> > flowFile.getAttributes().entrySet().stream().filter(e ->
> > e.getKey().startsWith("foo"))
> >.forEach(e -> session.putAttribute(flowFile, "original-" + e.getKey,
> > e.getValue()));
> >
> > and I wondered how that could possibly work since the return value of
> > session.putAttribute is ignored! Now I know.
> >
> > -- Mike
> >
> > On Tue, May 7, 2024 at 3:02 PM Russell Bateman
> > wrote:
> >
> >> Yes, what you described is what was happening, Mark. I didn't display
> >> all of the code to the session methods, and I did re-read the in-coming
> >> flowfile for different purposes than I had already read and written it.
> >> So, I wasn't helpful enough. In the end, however, I had forgotten,
> >> immediately after the call to session.putAllAttributes(), to update the
> >> resulting flowfile for passing to session.transfer(). That solved it for
> >> 1.1.2 which wasn't necessary for 1.13.2 or later versions. Being
> >> helpful, the newer versions made me a spoiled, entitled child and I will
> >> repent immediately.
> >>
> >> Thanks, guys! DevOps are happy they don't have to upgrade the customers
> >> to NiFi 1.13.2. (In a way, I'm unhappy about that, but...).
> >>
> >> Best regards,
> >>
> >> Russ
> >>
> >> On 5/7/24 11:53, Mark Payne wrote:
> >>> The call to session.putAttribute would throw an Exception because you
> >>> provided an outdated version of the flowFile (did not capturing the
> >>> result of calling session.write)
> >>>
> >>> Now, as NiFi matured, we found that:
> >>> (a) for more complex processors that aren’t just a series of sequential
> >>> steps it becomes difficult to manage all of that bookkeeping.
> >>> (b) it was not intuitive to require this
> >>> (c) the ProcessSession already had more or less what it needed in order
> >>> to determine what the most up-to-date version of the FlowFile was.
> >>>
> >>> So we updated the ProcessSession to automatically grab the latest
> >>> version of the FlowFile for these methods. But since you’re trying to
> >>> run an old version, you’ll need to make sure that you capture all of
> >>> those outputs and always keep track of the most recent version of a
> >>> FlowFile.
> >>
>
>
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC3)
Thanks Joe! Then it's probably the same build issue we found with this version. Regards, Gabor On Wed, 8 May 2024 at 21:32, Joe Witt wrote: > pkgutil --pkg-info=com.apple.pkg.CLTools_Executables > package-id: com.apple.pkg.CLTools_Executables > version: 15.3.0.0.1.1708646388 > volume: / > location: / > install-time: 1710790868 > sw_vers > ProductName: macOS > ProductVersion: 14.4.1 > BuildVersion: 23E224 > > Thanks > Joe > > > On Wed, May 8, 2024 at 8:15 AM Gábor Gyimesi wrote: > > > For checking the xcode version you can use the following command: > > $ pkgutil --pkg-info=com.apple.pkg.CLTools_Executables > > And to check the macos version use the following command: > > $ sw_vers > > > > On Wed, 8 May 2024 at 16:35, Gábor Gyimesi wrote: > > > > > The build output should be visible on the stdout and stderr channels so > > > the output should be visible above the python output. If it is hidden > for > > > some reason when you use the python bootstrap, you could use the cmake > > > commands to rerun the build with the default extensions: > > > $ mkdir build && cd build && cmake -G Ninja .. && cmake --build . > > --target > > > package > > > > > > BR, > > > Gabor > > > > > > On Wed, 8 May 2024 at 16:23, Joe Witt wrote: > > > > > >> Gabor - thanks. Can you share a specific command and/or file I can > look > > >> at > > >> which would have the good info? > > >> > > >> On Wed, May 8, 2024 at 7:00 AM Gábor Gyimesi > > >> wrote: > > >> > > >> > Hi Team, > > >> > > > >> > In light of the issues found on the MacOS platform I am canceling > RC3 > > >> and > > >> > will create RC4 once the issues are resolved. > > >> > > > >> > Two of the runtime issues have already been addressed by these 2 > PRs: > > >> > https://github.com/apache/nifi-minifi-cpp/pull/1782 > > >> > https://github.com/apache/nifi-minifi-cpp/pull/1783 > > >> > > > >> > The investigation of the build issues on the latest MacOS version is > > >> still > > >> > ongoing. > > >> > > > >> > @Joe can you confirm that your build issue is on the MacOS version > > >> 14.4.1 > > >> > with xcode 15.3 or that it is due to the flex issue Adam mentioned? > > >> > Otherwise please share the issue so we could check that one out as > > well. > > >> > > > >> > Thanks, > > >> > Gabor > > >> > > > >> > On Wed, 8 May 2024 at 15:40, Adam Debreceni > > >> wrote: > > >> > > > >> > > -1 (non-binding) > > >> > > > > >> > > Verified signatures/hashes, compiled on macos 14.2.1 with xcode > 15.1 > > >> and > > >> > > deployed simple flow through c2 protocol, > > >> > > but I have found the following on macos: > > >> > > - getting errors running nifi python processors, due to python > > >> > searching > > >> > > for minifi_native.so > > >> > > - minifi.plist is missing from the package making it impossible > to > > >> > > install the agent as a service > > >> > > > > >> > > (We also have to be mindful about the flex package as either we > use > > >> the > > >> > > system flex or the brew flex > > >> > > but for the latter both the PATH and the CMAKE_CXX_FLAGS should be > > set > > >> > > accordingly) > > >> > > > > >> > > We also found that it does not compile on the newest macos 14.4.1 > > with > > >> > > xcode 15.3. > > >> > > > > >> > > On Wed, May 8, 2024 at 1:15 PM Martin Zink > > > >> > wrote: > > >> > > > > >> > > > +1 (non-binding) > > >> > > > > > >> > > > -Verified signature, hashes and git commit hash > > >> > > > -Built it from source with default extensions on RockyLinux 9 > > >> (aarch64 > > >> > > > and x86_64), macOS 14.3.1 (M1) and Windows 10 (x86_64) using the > > new > > >> > > > python based bootstrap > > >> > > > -Ran through a couple of C2 initiated flows > > >> > > > > > >> > > > Everything worked as expected, > > >> > > > > > >> > > > > > >> > > > thanks Gabor for RMing great work, > > >> > > > Martin > > >> > > > > > >> > > > > > >> > > > On Wed, May 8, 2024 at 9:18 AM Gábor Gyimesi < > > lordga...@apache.org> > > >> > > wrote: > > >> > > > > > > >> > > > > Hi Joe, > > >> > > > > > > >> > > > > Could you check the ninja output for the build error? The > output > > >> you > > >> > > sent > > >> > > > > is only the bootstrap script's traceback of the build step's > > >> failure, > > >> > > but > > >> > > > > there should probably be an error in the build output as well > > >> > starting > > >> > > > with > > >> > > > > "error: ". > > >> > > > > > > >> > > > > BR, > > >> > > > > Gabor > > >> > > > > > > >> > > > > On Wed, 8 May 2024 at 02:26, Joe Witt > > wrote: > > >> > > > > > > >> > > > > > Hello > > >> > > > > > > > >> > > > > > Sigs/Hashes are good. > > >> > > > > > > > >> > > > > > Building source on macos I'm getting a build failure. The > > only > > >> > > option > > >> > > > > > selected was to skip tests otherwise left as defaults. Am > > >> > following > > >> > > > the > > >> > > > > > readme and release guide. > > >> > > > > > > > >> > > > > > ninja: build stopped: subcommand failed. > > >> > > > > > Build was unsuccessful > > >>
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC3)
pkgutil --pkg-info=com.apple.pkg.CLTools_Executables package-id: com.apple.pkg.CLTools_Executables version: 15.3.0.0.1.1708646388 volume: / location: / install-time: 1710790868 sw_vers ProductName: macOS ProductVersion: 14.4.1 BuildVersion: 23E224 Thanks Joe On Wed, May 8, 2024 at 8:15 AM Gábor Gyimesi wrote: > For checking the xcode version you can use the following command: > $ pkgutil --pkg-info=com.apple.pkg.CLTools_Executables > And to check the macos version use the following command: > $ sw_vers > > On Wed, 8 May 2024 at 16:35, Gábor Gyimesi wrote: > > > The build output should be visible on the stdout and stderr channels so > > the output should be visible above the python output. If it is hidden for > > some reason when you use the python bootstrap, you could use the cmake > > commands to rerun the build with the default extensions: > > $ mkdir build && cd build && cmake -G Ninja .. && cmake --build . > --target > > package > > > > BR, > > Gabor > > > > On Wed, 8 May 2024 at 16:23, Joe Witt wrote: > > > >> Gabor - thanks. Can you share a specific command and/or file I can look > >> at > >> which would have the good info? > >> > >> On Wed, May 8, 2024 at 7:00 AM Gábor Gyimesi > >> wrote: > >> > >> > Hi Team, > >> > > >> > In light of the issues found on the MacOS platform I am canceling RC3 > >> and > >> > will create RC4 once the issues are resolved. > >> > > >> > Two of the runtime issues have already been addressed by these 2 PRs: > >> > https://github.com/apache/nifi-minifi-cpp/pull/1782 > >> > https://github.com/apache/nifi-minifi-cpp/pull/1783 > >> > > >> > The investigation of the build issues on the latest MacOS version is > >> still > >> > ongoing. > >> > > >> > @Joe can you confirm that your build issue is on the MacOS version > >> 14.4.1 > >> > with xcode 15.3 or that it is due to the flex issue Adam mentioned? > >> > Otherwise please share the issue so we could check that one out as > well. > >> > > >> > Thanks, > >> > Gabor > >> > > >> > On Wed, 8 May 2024 at 15:40, Adam Debreceni > >> wrote: > >> > > >> > > -1 (non-binding) > >> > > > >> > > Verified signatures/hashes, compiled on macos 14.2.1 with xcode 15.1 > >> and > >> > > deployed simple flow through c2 protocol, > >> > > but I have found the following on macos: > >> > > - getting errors running nifi python processors, due to python > >> > searching > >> > > for minifi_native.so > >> > > - minifi.plist is missing from the package making it impossible to > >> > > install the agent as a service > >> > > > >> > > (We also have to be mindful about the flex package as either we use > >> the > >> > > system flex or the brew flex > >> > > but for the latter both the PATH and the CMAKE_CXX_FLAGS should be > set > >> > > accordingly) > >> > > > >> > > We also found that it does not compile on the newest macos 14.4.1 > with > >> > > xcode 15.3. > >> > > > >> > > On Wed, May 8, 2024 at 1:15 PM Martin Zink > >> > wrote: > >> > > > >> > > > +1 (non-binding) > >> > > > > >> > > > -Verified signature, hashes and git commit hash > >> > > > -Built it from source with default extensions on RockyLinux 9 > >> (aarch64 > >> > > > and x86_64), macOS 14.3.1 (M1) and Windows 10 (x86_64) using the > new > >> > > > python based bootstrap > >> > > > -Ran through a couple of C2 initiated flows > >> > > > > >> > > > Everything worked as expected, > >> > > > > >> > > > > >> > > > thanks Gabor for RMing great work, > >> > > > Martin > >> > > > > >> > > > > >> > > > On Wed, May 8, 2024 at 9:18 AM Gábor Gyimesi < > lordga...@apache.org> > >> > > wrote: > >> > > > > > >> > > > > Hi Joe, > >> > > > > > >> > > > > Could you check the ninja output for the build error? The output > >> you > >> > > sent > >> > > > > is only the bootstrap script's traceback of the build step's > >> failure, > >> > > but > >> > > > > there should probably be an error in the build output as well > >> > starting > >> > > > with > >> > > > > "error: ". > >> > > > > > >> > > > > BR, > >> > > > > Gabor > >> > > > > > >> > > > > On Wed, 8 May 2024 at 02:26, Joe Witt > wrote: > >> > > > > > >> > > > > > Hello > >> > > > > > > >> > > > > > Sigs/Hashes are good. > >> > > > > > > >> > > > > > Building source on macos I'm getting a build failure. The > only > >> > > option > >> > > > > > selected was to skip tests otherwise left as defaults. Am > >> > following > >> > > > the > >> > > > > > readme and release guide. > >> > > > > > > >> > > > > > ninja: build stopped: subcommand failed. > >> > > > > > Build was unsuccessful > >> > > > > > Traceback (most recent call last): > >> > > > > > File > >> > > > > > > >> > > > > > > >> > > > > >> > > > >> > > >> > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/main.py", > >> > > > > > line 62, in > >> > > > > > main_menu(minifi_options, package_manager) > >> > > > > > File > >> > > > > > > >> > > > > > > >> > > > > >> > > > >> > > >> > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC3)
For checking the xcode version you can use the following command: $ pkgutil --pkg-info=com.apple.pkg.CLTools_Executables And to check the macos version use the following command: $ sw_vers On Wed, 8 May 2024 at 16:35, Gábor Gyimesi wrote: > The build output should be visible on the stdout and stderr channels so > the output should be visible above the python output. If it is hidden for > some reason when you use the python bootstrap, you could use the cmake > commands to rerun the build with the default extensions: > $ mkdir build && cd build && cmake -G Ninja .. && cmake --build . --target > package > > BR, > Gabor > > On Wed, 8 May 2024 at 16:23, Joe Witt wrote: > >> Gabor - thanks. Can you share a specific command and/or file I can look >> at >> which would have the good info? >> >> On Wed, May 8, 2024 at 7:00 AM Gábor Gyimesi >> wrote: >> >> > Hi Team, >> > >> > In light of the issues found on the MacOS platform I am canceling RC3 >> and >> > will create RC4 once the issues are resolved. >> > >> > Two of the runtime issues have already been addressed by these 2 PRs: >> > https://github.com/apache/nifi-minifi-cpp/pull/1782 >> > https://github.com/apache/nifi-minifi-cpp/pull/1783 >> > >> > The investigation of the build issues on the latest MacOS version is >> still >> > ongoing. >> > >> > @Joe can you confirm that your build issue is on the MacOS version >> 14.4.1 >> > with xcode 15.3 or that it is due to the flex issue Adam mentioned? >> > Otherwise please share the issue so we could check that one out as well. >> > >> > Thanks, >> > Gabor >> > >> > On Wed, 8 May 2024 at 15:40, Adam Debreceni >> wrote: >> > >> > > -1 (non-binding) >> > > >> > > Verified signatures/hashes, compiled on macos 14.2.1 with xcode 15.1 >> and >> > > deployed simple flow through c2 protocol, >> > > but I have found the following on macos: >> > > - getting errors running nifi python processors, due to python >> > searching >> > > for minifi_native.so >> > > - minifi.plist is missing from the package making it impossible to >> > > install the agent as a service >> > > >> > > (We also have to be mindful about the flex package as either we use >> the >> > > system flex or the brew flex >> > > but for the latter both the PATH and the CMAKE_CXX_FLAGS should be set >> > > accordingly) >> > > >> > > We also found that it does not compile on the newest macos 14.4.1 with >> > > xcode 15.3. >> > > >> > > On Wed, May 8, 2024 at 1:15 PM Martin Zink >> > wrote: >> > > >> > > > +1 (non-binding) >> > > > >> > > > -Verified signature, hashes and git commit hash >> > > > -Built it from source with default extensions on RockyLinux 9 >> (aarch64 >> > > > and x86_64), macOS 14.3.1 (M1) and Windows 10 (x86_64) using the new >> > > > python based bootstrap >> > > > -Ran through a couple of C2 initiated flows >> > > > >> > > > Everything worked as expected, >> > > > >> > > > >> > > > thanks Gabor for RMing great work, >> > > > Martin >> > > > >> > > > >> > > > On Wed, May 8, 2024 at 9:18 AM Gábor Gyimesi >> > > wrote: >> > > > > >> > > > > Hi Joe, >> > > > > >> > > > > Could you check the ninja output for the build error? The output >> you >> > > sent >> > > > > is only the bootstrap script's traceback of the build step's >> failure, >> > > but >> > > > > there should probably be an error in the build output as well >> > starting >> > > > with >> > > > > "error: ". >> > > > > >> > > > > BR, >> > > > > Gabor >> > > > > >> > > > > On Wed, 8 May 2024 at 02:26, Joe Witt wrote: >> > > > > >> > > > > > Hello >> > > > > > >> > > > > > Sigs/Hashes are good. >> > > > > > >> > > > > > Building source on macos I'm getting a build failure. The only >> > > option >> > > > > > selected was to skip tests otherwise left as defaults. Am >> > following >> > > > the >> > > > > > readme and release guide. >> > > > > > >> > > > > > ninja: build stopped: subcommand failed. >> > > > > > Build was unsuccessful >> > > > > > Traceback (most recent call last): >> > > > > > File >> > > > > > >> > > > > > >> > > > >> > > >> > >> "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/main.py", >> > > > > > line 62, in >> > > > > > main_menu(minifi_options, package_manager) >> > > > > > File >> > > > > > >> > > > > > >> > > > >> > > >> > >> "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/cli.py", >> > > > > > line 87, in main_menu >> > > > > > done = >> > > > main_menu_options[main_menu_prompt["sub_menu"]](minifi_options, >> > > > > > package_manager) >> > > > > > >> > > > > > >> > > > > > >> > > > >> > > >> > >> >> > > > > > File >> > > > > > >> > > > > > >> > > > >> > > >> > >> "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/cli.py", >> > > > > > line 60, in do_one_click_build >> > > > > > assert do_build(minifi_options, package_manager) >> > > > > > >> > > > > > >> > > >
Re: ...not the most recent version of this FlowFile within this session...
Yeah, that was something that kinda flew under the radar. Definitely improved
the API.
Not really related, but on the note of things you may not realize, with that
code snippet :)
If you have access to update the processor mentioned here, you should avoid
using session.putAttribute many times.
Under the hood, in order to maintain object immutability it has to create a new
FlowFile object (and a new HashMap of all attributes!)
for every call to putAttribute. So if there are 100 attributes that match
that’s potentially a huge amount of garbage getting created. Instead,
you could just use:
```
final Map attributes = new HashMap<>();
flowFile.getAttributes().forEach( (key, value) -> {
if (key.startsWith(“foo”)) {
attributes.put(“original-“ + key, value);
}
}
flowFIle = session.putAllAttributes(flowFile, attributes);
```
Thanks
-Mark
> On May 8, 2024, at 10:30 AM, Michael Moser wrote:
>
> Wow, thanks for this information! Just last week I saw code that modified
> attributes in a stream:
>
> flowFile.getAttributes().entrySet().stream().filter(e ->
> e.getKey().startsWith("foo"))
>.forEach(e -> session.putAttribute(flowFile, "original-" + e.getKey,
> e.getValue()));
>
> and I wondered how that could possibly work since the return value of
> session.putAttribute is ignored! Now I know.
>
> -- Mike
>
> On Tue, May 7, 2024 at 3:02 PM Russell Bateman
> wrote:
>
>> Yes, what you described is what was happening, Mark. I didn't display
>> all of the code to the session methods, and I did re-read the in-coming
>> flowfile for different purposes than I had already read and written it.
>> So, I wasn't helpful enough. In the end, however, I had forgotten,
>> immediately after the call to session.putAllAttributes(), to update the
>> resulting flowfile for passing to session.transfer(). That solved it for
>> 1.1.2 which wasn't necessary for 1.13.2 or later versions. Being
>> helpful, the newer versions made me a spoiled, entitled child and I will
>> repent immediately.
>>
>> Thanks, guys! DevOps are happy they don't have to upgrade the customers
>> to NiFi 1.13.2. (In a way, I'm unhappy about that, but...).
>>
>> Best regards,
>>
>> Russ
>>
>> On 5/7/24 11:53, Mark Payne wrote:
>>> The call to session.putAttribute would throw an Exception because you
>>> provided an outdated version of the flowFile (did not capturing the
>>> result of calling session.write)
>>>
>>> Now, as NiFi matured, we found that:
>>> (a) for more complex processors that aren’t just a series of sequential
>>> steps it becomes difficult to manage all of that bookkeeping.
>>> (b) it was not intuitive to require this
>>> (c) the ProcessSession already had more or less what it needed in order
>>> to determine what the most up-to-date version of the FlowFile was.
>>>
>>> So we updated the ProcessSession to automatically grab the latest
>>> version of the FlowFile for these methods. But since you’re trying to
>>> run an old version, you’ll need to make sure that you capture all of
>>> those outputs and always keep track of the most recent version of a
>>> FlowFile.
>>
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC3)
The build output should be visible on the stdout and stderr channels so the output should be visible above the python output. If it is hidden for some reason when you use the python bootstrap, you could use the cmake commands to rerun the build with the default extensions: $ mkdir build && cd build && cmake -G Ninja .. && cmake --build . --target package BR, Gabor On Wed, 8 May 2024 at 16:23, Joe Witt wrote: > Gabor - thanks. Can you share a specific command and/or file I can look at > which would have the good info? > > On Wed, May 8, 2024 at 7:00 AM Gábor Gyimesi wrote: > > > Hi Team, > > > > In light of the issues found on the MacOS platform I am canceling RC3 and > > will create RC4 once the issues are resolved. > > > > Two of the runtime issues have already been addressed by these 2 PRs: > > https://github.com/apache/nifi-minifi-cpp/pull/1782 > > https://github.com/apache/nifi-minifi-cpp/pull/1783 > > > > The investigation of the build issues on the latest MacOS version is > still > > ongoing. > > > > @Joe can you confirm that your build issue is on the MacOS version 14.4.1 > > with xcode 15.3 or that it is due to the flex issue Adam mentioned? > > Otherwise please share the issue so we could check that one out as well. > > > > Thanks, > > Gabor > > > > On Wed, 8 May 2024 at 15:40, Adam Debreceni > wrote: > > > > > -1 (non-binding) > > > > > > Verified signatures/hashes, compiled on macos 14.2.1 with xcode 15.1 > and > > > deployed simple flow through c2 protocol, > > > but I have found the following on macos: > > > - getting errors running nifi python processors, due to python > > searching > > > for minifi_native.so > > > - minifi.plist is missing from the package making it impossible to > > > install the agent as a service > > > > > > (We also have to be mindful about the flex package as either we use the > > > system flex or the brew flex > > > but for the latter both the PATH and the CMAKE_CXX_FLAGS should be set > > > accordingly) > > > > > > We also found that it does not compile on the newest macos 14.4.1 with > > > xcode 15.3. > > > > > > On Wed, May 8, 2024 at 1:15 PM Martin Zink > > wrote: > > > > > > > +1 (non-binding) > > > > > > > > -Verified signature, hashes and git commit hash > > > > -Built it from source with default extensions on RockyLinux 9 > (aarch64 > > > > and x86_64), macOS 14.3.1 (M1) and Windows 10 (x86_64) using the new > > > > python based bootstrap > > > > -Ran through a couple of C2 initiated flows > > > > > > > > Everything worked as expected, > > > > > > > > > > > > thanks Gabor for RMing great work, > > > > Martin > > > > > > > > > > > > On Wed, May 8, 2024 at 9:18 AM Gábor Gyimesi > > > wrote: > > > > > > > > > > Hi Joe, > > > > > > > > > > Could you check the ninja output for the build error? The output > you > > > sent > > > > > is only the bootstrap script's traceback of the build step's > failure, > > > but > > > > > there should probably be an error in the build output as well > > starting > > > > with > > > > > "error: ". > > > > > > > > > > BR, > > > > > Gabor > > > > > > > > > > On Wed, 8 May 2024 at 02:26, Joe Witt wrote: > > > > > > > > > > > Hello > > > > > > > > > > > > Sigs/Hashes are good. > > > > > > > > > > > > Building source on macos I'm getting a build failure. The only > > > option > > > > > > selected was to skip tests otherwise left as defaults. Am > > following > > > > the > > > > > > readme and release guide. > > > > > > > > > > > > ninja: build stopped: subcommand failed. > > > > > > Build was unsuccessful > > > > > > Traceback (most recent call last): > > > > > > File > > > > > > > > > > > > > > > > > > > > > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/main.py", > > > > > > line 62, in > > > > > > main_menu(minifi_options, package_manager) > > > > > > File > > > > > > > > > > > > > > > > > > > > > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/cli.py", > > > > > > line 87, in main_menu > > > > > > done = > > > > main_menu_options[main_menu_prompt["sub_menu"]](minifi_options, > > > > > > package_manager) > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > File > > > > > > > > > > > > > > > > > > > > > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/cli.py", > > > > > > line 60, in do_one_click_build > > > > > > assert do_build(minifi_options, package_manager) > > > > > > > > > > > > > > > > > > So then I select to not use ninja and run the one click build > > again. > > > > > > It seems to run for much longer then the same output prints > again. > > > > > > > > > > > > Thanks > > > > > > Joe > > > > > > > > > > > > On Tue, May 7, 2024 at 9:45 AM Arpad Boda > > wrote: > > > > > > > > > > > > > +1 (binding) > > > > > > > > > > > > > > Built on ubuntu, verified signature and checksums. All tests > > > p
Re: ...not the most recent version of this FlowFile within this session...
Wow, thanks for this information! Just last week I saw code that modified
attributes in a stream:
flowFile.getAttributes().entrySet().stream().filter(e ->
e.getKey().startsWith("foo"))
.forEach(e -> session.putAttribute(flowFile, "original-" + e.getKey,
e.getValue()));
and I wondered how that could possibly work since the return value of
session.putAttribute is ignored! Now I know.
-- Mike
On Tue, May 7, 2024 at 3:02 PM Russell Bateman
wrote:
> Yes, what you described is what was happening, Mark. I didn't display
> all of the code to the session methods, and I did re-read the in-coming
> flowfile for different purposes than I had already read and written it.
> So, I wasn't helpful enough. In the end, however, I had forgotten,
> immediately after the call to session.putAllAttributes(), to update the
> resulting flowfile for passing to session.transfer(). That solved it for
> 1.1.2 which wasn't necessary for 1.13.2 or later versions. Being
> helpful, the newer versions made me a spoiled, entitled child and I will
> repent immediately.
>
> Thanks, guys! DevOps are happy they don't have to upgrade the customers
> to NiFi 1.13.2. (In a way, I'm unhappy about that, but...).
>
> Best regards,
>
> Russ
>
> On 5/7/24 11:53, Mark Payne wrote:
> > The call to session.putAttribute would throw an Exception because you
> > provided an outdated version of the flowFile (did not capturing the
> > result of calling session.write)
> >
> > Now, as NiFi matured, we found that:
> > (a) for more complex processors that aren’t just a series of sequential
> > steps it becomes difficult to manage all of that bookkeeping.
> > (b) it was not intuitive to require this
> > (c) the ProcessSession already had more or less what it needed in order
> > to determine what the most up-to-date version of the FlowFile was.
> >
> > So we updated the ProcessSession to automatically grab the latest
> > version of the FlowFile for these methods. But since you’re trying to
> > run an old version, you’ll need to make sure that you capture all of
> > those outputs and always keep track of the most recent version of a
> > FlowFile.
>
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC3)
Gabor - thanks. Can you share a specific command and/or file I can look at which would have the good info? On Wed, May 8, 2024 at 7:00 AM Gábor Gyimesi wrote: > Hi Team, > > In light of the issues found on the MacOS platform I am canceling RC3 and > will create RC4 once the issues are resolved. > > Two of the runtime issues have already been addressed by these 2 PRs: > https://github.com/apache/nifi-minifi-cpp/pull/1782 > https://github.com/apache/nifi-minifi-cpp/pull/1783 > > The investigation of the build issues on the latest MacOS version is still > ongoing. > > @Joe can you confirm that your build issue is on the MacOS version 14.4.1 > with xcode 15.3 or that it is due to the flex issue Adam mentioned? > Otherwise please share the issue so we could check that one out as well. > > Thanks, > Gabor > > On Wed, 8 May 2024 at 15:40, Adam Debreceni wrote: > > > -1 (non-binding) > > > > Verified signatures/hashes, compiled on macos 14.2.1 with xcode 15.1 and > > deployed simple flow through c2 protocol, > > but I have found the following on macos: > > - getting errors running nifi python processors, due to python > searching > > for minifi_native.so > > - minifi.plist is missing from the package making it impossible to > > install the agent as a service > > > > (We also have to be mindful about the flex package as either we use the > > system flex or the brew flex > > but for the latter both the PATH and the CMAKE_CXX_FLAGS should be set > > accordingly) > > > > We also found that it does not compile on the newest macos 14.4.1 with > > xcode 15.3. > > > > On Wed, May 8, 2024 at 1:15 PM Martin Zink > wrote: > > > > > +1 (non-binding) > > > > > > -Verified signature, hashes and git commit hash > > > -Built it from source with default extensions on RockyLinux 9 (aarch64 > > > and x86_64), macOS 14.3.1 (M1) and Windows 10 (x86_64) using the new > > > python based bootstrap > > > -Ran through a couple of C2 initiated flows > > > > > > Everything worked as expected, > > > > > > > > > thanks Gabor for RMing great work, > > > Martin > > > > > > > > > On Wed, May 8, 2024 at 9:18 AM Gábor Gyimesi > > wrote: > > > > > > > > Hi Joe, > > > > > > > > Could you check the ninja output for the build error? The output you > > sent > > > > is only the bootstrap script's traceback of the build step's failure, > > but > > > > there should probably be an error in the build output as well > starting > > > with > > > > "error: ". > > > > > > > > BR, > > > > Gabor > > > > > > > > On Wed, 8 May 2024 at 02:26, Joe Witt wrote: > > > > > > > > > Hello > > > > > > > > > > Sigs/Hashes are good. > > > > > > > > > > Building source on macos I'm getting a build failure. The only > > option > > > > > selected was to skip tests otherwise left as defaults. Am > following > > > the > > > > > readme and release guide. > > > > > > > > > > ninja: build stopped: subcommand failed. > > > > > Build was unsuccessful > > > > > Traceback (most recent call last): > > > > > File > > > > > > > > > > > > > > > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/main.py", > > > > > line 62, in > > > > > main_menu(minifi_options, package_manager) > > > > > File > > > > > > > > > > > > > > > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/cli.py", > > > > > line 87, in main_menu > > > > > done = > > > main_menu_options[main_menu_prompt["sub_menu"]](minifi_options, > > > > > package_manager) > > > > > > > > > > > > > > > > > > > > > > > > > > File > > > > > > > > > > > > > > > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/cli.py", > > > > > line 60, in do_one_click_build > > > > > assert do_build(minifi_options, package_manager) > > > > > > > > > > > > > > > So then I select to not use ninja and run the one click build > again. > > > > > It seems to run for much longer then the same output prints again. > > > > > > > > > > Thanks > > > > > Joe > > > > > > > > > > On Tue, May 7, 2024 at 9:45 AM Arpad Boda > wrote: > > > > > > > > > > > +1 (binding) > > > > > > > > > > > > Built on ubuntu, verified signature and checksums. All tests > > passed, > > > > > > started and ran a simple flow with no issues. > > > > > > > > > > > > Nice job, team! > > > > > > > > > > > > On Tue, May 7, 2024 at 11:35 AM Gábor Gyimesi < > > lordga...@apache.org> > > > > > > wrote: > > > > > > > > > > > > > Hello, > > > > > > > > > > > > > > I am pleased to be calling this vote for the source release of > > > Apache > > > > > > NiFi > > > > > > > MiNiFi C++ 0.99.0. > > > > > > > > > > > > > > The source tarball, some binary builds, plus signatures and > > > digests can > > > > > > be > > > > > > > found at: > > > > > > > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/ > > > > > > > > > > > > > > The Git tag is minifi-cpp-0.99.0-RC3 > > > > > > > The
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC3)
Hi Team, In light of the issues found on the MacOS platform I am canceling RC3 and will create RC4 once the issues are resolved. Two of the runtime issues have already been addressed by these 2 PRs: https://github.com/apache/nifi-minifi-cpp/pull/1782 https://github.com/apache/nifi-minifi-cpp/pull/1783 The investigation of the build issues on the latest MacOS version is still ongoing. @Joe can you confirm that your build issue is on the MacOS version 14.4.1 with xcode 15.3 or that it is due to the flex issue Adam mentioned? Otherwise please share the issue so we could check that one out as well. Thanks, Gabor On Wed, 8 May 2024 at 15:40, Adam Debreceni wrote: > -1 (non-binding) > > Verified signatures/hashes, compiled on macos 14.2.1 with xcode 15.1 and > deployed simple flow through c2 protocol, > but I have found the following on macos: > - getting errors running nifi python processors, due to python searching > for minifi_native.so > - minifi.plist is missing from the package making it impossible to > install the agent as a service > > (We also have to be mindful about the flex package as either we use the > system flex or the brew flex > but for the latter both the PATH and the CMAKE_CXX_FLAGS should be set > accordingly) > > We also found that it does not compile on the newest macos 14.4.1 with > xcode 15.3. > > On Wed, May 8, 2024 at 1:15 PM Martin Zink wrote: > > > +1 (non-binding) > > > > -Verified signature, hashes and git commit hash > > -Built it from source with default extensions on RockyLinux 9 (aarch64 > > and x86_64), macOS 14.3.1 (M1) and Windows 10 (x86_64) using the new > > python based bootstrap > > -Ran through a couple of C2 initiated flows > > > > Everything worked as expected, > > > > > > thanks Gabor for RMing great work, > > Martin > > > > > > On Wed, May 8, 2024 at 9:18 AM Gábor Gyimesi > wrote: > > > > > > Hi Joe, > > > > > > Could you check the ninja output for the build error? The output you > sent > > > is only the bootstrap script's traceback of the build step's failure, > but > > > there should probably be an error in the build output as well starting > > with > > > "error: ". > > > > > > BR, > > > Gabor > > > > > > On Wed, 8 May 2024 at 02:26, Joe Witt wrote: > > > > > > > Hello > > > > > > > > Sigs/Hashes are good. > > > > > > > > Building source on macos I'm getting a build failure. The only > option > > > > selected was to skip tests otherwise left as defaults. Am following > > the > > > > readme and release guide. > > > > > > > > ninja: build stopped: subcommand failed. > > > > Build was unsuccessful > > > > Traceback (most recent call last): > > > > File > > > > > > > > > > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/main.py", > > > > line 62, in > > > > main_menu(minifi_options, package_manager) > > > > File > > > > > > > > > > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/cli.py", > > > > line 87, in main_menu > > > > done = > > main_menu_options[main_menu_prompt["sub_menu"]](minifi_options, > > > > package_manager) > > > > > > > > > > > > > > > > > > > File > > > > > > > > > > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/cli.py", > > > > line 60, in do_one_click_build > > > > assert do_build(minifi_options, package_manager) > > > > > > > > > > > > So then I select to not use ninja and run the one click build again. > > > > It seems to run for much longer then the same output prints again. > > > > > > > > Thanks > > > > Joe > > > > > > > > On Tue, May 7, 2024 at 9:45 AM Arpad Boda wrote: > > > > > > > > > +1 (binding) > > > > > > > > > > Built on ubuntu, verified signature and checksums. All tests > passed, > > > > > started and ran a simple flow with no issues. > > > > > > > > > > Nice job, team! > > > > > > > > > > On Tue, May 7, 2024 at 11:35 AM Gábor Gyimesi < > lordga...@apache.org> > > > > > wrote: > > > > > > > > > > > Hello, > > > > > > > > > > > > I am pleased to be calling this vote for the source release of > > Apache > > > > > NiFi > > > > > > MiNiFi C++ 0.99.0. > > > > > > > > > > > > The source tarball, some binary builds, plus signatures and > > digests can > > > > > be > > > > > > found at: > > > > > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/ > > > > > > > > > > > > The Git tag is minifi-cpp-0.99.0-RC3 > > > > > > The Git commit ID is d3d205f3c8a8376bbad4c8a47758d585d57c653b > > > > > > > > > > > > > > > > > > > > > > > > https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=d3d205f3c8a8376bbad4c8a47758d585d57c653b > > > > > > > > > > > > Checksums of nifi-minifi-cpp-0.99.0-source.tar.gz: > > > > > > SHA256: > > > > c00ff309776720b295cb52ab12c1c3d11182af4f19ed0a379d58f96b16841059 > > > > > > SHA512: > > > > > > > > > > > > > > > > > > > > > > > > d1eda2c19da8f0e073cf460bf
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC3)
-1 (non-binding) Verified signatures/hashes, compiled on macos 14.2.1 with xcode 15.1 and deployed simple flow through c2 protocol, but I have found the following on macos: - getting errors running nifi python processors, due to python searching for minifi_native.so - minifi.plist is missing from the package making it impossible to install the agent as a service (We also have to be mindful about the flex package as either we use the system flex or the brew flex but for the latter both the PATH and the CMAKE_CXX_FLAGS should be set accordingly) We also found that it does not compile on the newest macos 14.4.1 with xcode 15.3. On Wed, May 8, 2024 at 1:15 PM Martin Zink wrote: > +1 (non-binding) > > -Verified signature, hashes and git commit hash > -Built it from source with default extensions on RockyLinux 9 (aarch64 > and x86_64), macOS 14.3.1 (M1) and Windows 10 (x86_64) using the new > python based bootstrap > -Ran through a couple of C2 initiated flows > > Everything worked as expected, > > > thanks Gabor for RMing great work, > Martin > > > On Wed, May 8, 2024 at 9:18 AM Gábor Gyimesi wrote: > > > > Hi Joe, > > > > Could you check the ninja output for the build error? The output you sent > > is only the bootstrap script's traceback of the build step's failure, but > > there should probably be an error in the build output as well starting > with > > "error: ". > > > > BR, > > Gabor > > > > On Wed, 8 May 2024 at 02:26, Joe Witt wrote: > > > > > Hello > > > > > > Sigs/Hashes are good. > > > > > > Building source on macos I'm getting a build failure. The only option > > > selected was to skip tests otherwise left as defaults. Am following > the > > > readme and release guide. > > > > > > ninja: build stopped: subcommand failed. > > > Build was unsuccessful > > > Traceback (most recent call last): > > > File > > > > > > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/main.py", > > > line 62, in > > > main_menu(minifi_options, package_manager) > > > File > > > > > > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/cli.py", > > > line 87, in main_menu > > > done = > main_menu_options[main_menu_prompt["sub_menu"]](minifi_options, > > > package_manager) > > > > > > > > > > > > > File > > > > > > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/cli.py", > > > line 60, in do_one_click_build > > > assert do_build(minifi_options, package_manager) > > > > > > > > > So then I select to not use ninja and run the one click build again. > > > It seems to run for much longer then the same output prints again. > > > > > > Thanks > > > Joe > > > > > > On Tue, May 7, 2024 at 9:45 AM Arpad Boda wrote: > > > > > > > +1 (binding) > > > > > > > > Built on ubuntu, verified signature and checksums. All tests passed, > > > > started and ran a simple flow with no issues. > > > > > > > > Nice job, team! > > > > > > > > On Tue, May 7, 2024 at 11:35 AM Gábor Gyimesi > > > > wrote: > > > > > > > > > Hello, > > > > > > > > > > I am pleased to be calling this vote for the source release of > Apache > > > > NiFi > > > > > MiNiFi C++ 0.99.0. > > > > > > > > > > The source tarball, some binary builds, plus signatures and > digests can > > > > be > > > > > found at: > > > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/ > > > > > > > > > > The Git tag is minifi-cpp-0.99.0-RC3 > > > > > The Git commit ID is d3d205f3c8a8376bbad4c8a47758d585d57c653b > > > > > > > > > > > > > > > > > > https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=d3d205f3c8a8376bbad4c8a47758d585d57c653b > > > > > > > > > > Checksums of nifi-minifi-cpp-0.99.0-source.tar.gz: > > > > > SHA256: > > > c00ff309776720b295cb52ab12c1c3d11182af4f19ed0a379d58f96b16841059 > > > > > SHA512: > > > > > > > > > > > > > > > > > > d1eda2c19da8f0e073cf460bf889c8b4a1b893de4b245dc0147d1c79545d5298c74bedf585afd7091dc9474c923fc2a7075a81a6397bedce310e5838e3afa898 > > > > > > > > > > Release artifacts are signed with the following key: > > > > > https://people.apache.org/keys/committer/lordgamez.asc > > > > > > > > > > A helpful reminder on how the release candidate verification > process > > > > works: > > > > > > > > > > > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087303 > > > > > > > > > > KEYS file available here: > > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > > > > > 121 issues were closed/resolved for this release: > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520&version=12353618 > > > > > > > > > > Release note highlights can be found here: > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.99.0 > > > > > > > > > > T
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC3)
+1 (non-binding) -Verified signature, hashes and git commit hash -Built it from source with default extensions on RockyLinux 9 (aarch64 and x86_64), macOS 14.3.1 (M1) and Windows 10 (x86_64) using the new python based bootstrap -Ran through a couple of C2 initiated flows Everything worked as expected, thanks Gabor for RMing great work, Martin On Wed, May 8, 2024 at 9:18 AM Gábor Gyimesi wrote: > > Hi Joe, > > Could you check the ninja output for the build error? The output you sent > is only the bootstrap script's traceback of the build step's failure, but > there should probably be an error in the build output as well starting with > "error: ". > > BR, > Gabor > > On Wed, 8 May 2024 at 02:26, Joe Witt wrote: > > > Hello > > > > Sigs/Hashes are good. > > > > Building source on macos I'm getting a build failure. The only option > > selected was to skip tests otherwise left as defaults. Am following the > > readme and release guide. > > > > ninja: build stopped: subcommand failed. > > Build was unsuccessful > > Traceback (most recent call last): > > File > > > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/main.py", > > line 62, in > > main_menu(minifi_options, package_manager) > > File > > > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/cli.py", > > line 87, in main_menu > > done = main_menu_options[main_menu_prompt["sub_menu"]](minifi_options, > > package_manager) > > > > > > > > > > File > > > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/cli.py", > > line 60, in do_one_click_build > > assert do_build(minifi_options, package_manager) > > > > > > So then I select to not use ninja and run the one click build again. > > It seems to run for much longer then the same output prints again. > > > > Thanks > > Joe > > > > On Tue, May 7, 2024 at 9:45 AM Arpad Boda wrote: > > > > > +1 (binding) > > > > > > Built on ubuntu, verified signature and checksums. All tests passed, > > > started and ran a simple flow with no issues. > > > > > > Nice job, team! > > > > > > On Tue, May 7, 2024 at 11:35 AM Gábor Gyimesi > > > wrote: > > > > > > > Hello, > > > > > > > > I am pleased to be calling this vote for the source release of Apache > > > NiFi > > > > MiNiFi C++ 0.99.0. > > > > > > > > The source tarball, some binary builds, plus signatures and digests can > > > be > > > > found at: > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/ > > > > > > > > The Git tag is minifi-cpp-0.99.0-RC3 > > > > The Git commit ID is d3d205f3c8a8376bbad4c8a47758d585d57c653b > > > > > > > > > > > > > https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=d3d205f3c8a8376bbad4c8a47758d585d57c653b > > > > > > > > Checksums of nifi-minifi-cpp-0.99.0-source.tar.gz: > > > > SHA256: > > c00ff309776720b295cb52ab12c1c3d11182af4f19ed0a379d58f96b16841059 > > > > SHA512: > > > > > > > > > > > > > d1eda2c19da8f0e073cf460bf889c8b4a1b893de4b245dc0147d1c79545d5298c74bedf585afd7091dc9474c923fc2a7075a81a6397bedce310e5838e3afa898 > > > > > > > > Release artifacts are signed with the following key: > > > > https://people.apache.org/keys/committer/lordgamez.asc > > > > > > > > A helpful reminder on how the release candidate verification process > > > works: > > > > > > > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087303 > > > > > > > > KEYS file available here: > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > > > 121 issues were closed/resolved for this release: > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520&version=12353618 > > > > > > > > Release note highlights can be found here: > > > > > > > > > > > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.99.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-minifi-cpp-0.99.0 > > > > [ ] +0 no opinion > > > > [ ] -1 Do not release this package because... > > > > > > > > >
Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC3)
Hi Joe, Could you check the ninja output for the build error? The output you sent is only the bootstrap script's traceback of the build step's failure, but there should probably be an error in the build output as well starting with "error: ". BR, Gabor On Wed, 8 May 2024 at 02:26, Joe Witt wrote: > Hello > > Sigs/Hashes are good. > > Building source on macos I'm getting a build failure. The only option > selected was to skip tests otherwise left as defaults. Am following the > readme and release guide. > > ninja: build stopped: subcommand failed. > Build was unsuccessful > Traceback (most recent call last): > File > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/main.py", > line 62, in > main_menu(minifi_options, package_manager) > File > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/cli.py", > line 87, in main_menu > done = main_menu_options[main_menu_prompt["sub_menu"]](minifi_options, > package_manager) > > > > > File > > "/Users/joe/development/build-verify/buld/nifi-minifi-cpp-0.99.0-source/bootstrap/cli.py", > line 60, in do_one_click_build > assert do_build(minifi_options, package_manager) > > > So then I select to not use ninja and run the one click build again. > It seems to run for much longer then the same output prints again. > > Thanks > Joe > > On Tue, May 7, 2024 at 9:45 AM Arpad Boda wrote: > > > +1 (binding) > > > > Built on ubuntu, verified signature and checksums. All tests passed, > > started and ran a simple flow with no issues. > > > > Nice job, team! > > > > On Tue, May 7, 2024 at 11:35 AM Gábor Gyimesi > > wrote: > > > > > Hello, > > > > > > I am pleased to be calling this vote for the source release of Apache > > NiFi > > > MiNiFi C++ 0.99.0. > > > > > > The source tarball, some binary builds, plus signatures and digests can > > be > > > found at: > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/ > > > > > > The Git tag is minifi-cpp-0.99.0-RC3 > > > The Git commit ID is d3d205f3c8a8376bbad4c8a47758d585d57c653b > > > > > > > > > https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=d3d205f3c8a8376bbad4c8a47758d585d57c653b > > > > > > Checksums of nifi-minifi-cpp-0.99.0-source.tar.gz: > > > SHA256: > c00ff309776720b295cb52ab12c1c3d11182af4f19ed0a379d58f96b16841059 > > > SHA512: > > > > > > > > > d1eda2c19da8f0e073cf460bf889c8b4a1b893de4b245dc0147d1c79545d5298c74bedf585afd7091dc9474c923fc2a7075a81a6397bedce310e5838e3afa898 > > > > > > Release artifacts are signed with the following key: > > > https://people.apache.org/keys/committer/lordgamez.asc > > > > > > A helpful reminder on how the release candidate verification process > > works: > > > > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087303 > > > > > > KEYS file available here: > > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > > > 121 issues were closed/resolved for this release: > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520&version=12353618 > > > > > > Release note highlights can be found here: > > > > > > > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.99.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-minifi-cpp-0.99.0 > > > [ ] +0 no opinion > > > [ ] -1 Do not release this package because... > > > > > >
