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:
>
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.
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
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.
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: /
>
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
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
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.
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
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
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
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
-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
+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
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
15 matches
Mail list logo
