Thanks for explaining the intent, David, and it makes perfect sense.
-- Mike
On Fri, Apr 19, 2024 at 12:26 PM David Handermann <
exceptionfact...@apache.org> wrote:
> Mike,
>
> The change was intentional from my understanding as Node.js 16 reached
> end of life last year [1]. Registry should
Mike,
The change was intentional from my understanding as Node.js 16 reached
end of life last year [1]. Registry should also be updated to build
with a more recent version of Node.js, but I believe there are some
details to sort out before that can be changed.
Regards,
David Handermann
[1]
Dan,
Reviewing recent changes, NIFI-13035 [1] updated the frontend build
process to use Node.js 21 for both the current nifi-web-ui and the new
nifi-web-frontend modules. For that reason, a more recent OS and glibc
version is now required.
Regards,
David Handermann
[1]
Perhaps this was an unintentional change to the nifi-web-ui from the
NIFI-13035 PR that was merged recently?
-- Mike
On Fri, Apr 19, 2024 at 12:06 PM Dan S wrote:
> Thanks David!
> I did not have this problem the other day when I submitted a PR for
> NIFI-12960.
>
> On Fri, Apr 19, 2024 at
Thanks David!
I did not have this problem the other day when I submitted a PR for
NIFI-12960.
On Fri, Apr 19, 2024 at 12:02 PM David Handermann <
exceptionfact...@apache.org> wrote:
> Dan,
>
> Reviewing the previous thread, the last reply from Matt Gilman still
> applies [1] meaning that CentOS
Dan,
Reviewing the previous thread, the last reply from Matt Gilman still
applies [1] meaning that CentOS 7 is not recent enough to support the
version of Node.js required.
CentOS 7 is also scheduled for End of Life [2] on June 30, 2024. Based
on the compatibility issues with the core OS
I am trying to build the 2.x branch for a PR I am trying to submit for
NIFI-13069 and it is failing. Here are the messages I see from the build
[INFO]
