Thanks for confirming. I haven't seen or heard of this hanging behavior
before from myself, other devs, or our CI builds. I wonder if there's
something running from a previous build that didn't complete gracefully.

Can you do a process listing and grep for nx? So something like...

ps -ef | grep nx
>

We set it up so that the nx daemon should be disabled during builds. So
unless you're manually running some nx commands for building/serving the UI
or otherwise you probably shouldn't see anything.  It might look
something like this...

/<path>/nifi/nifi-frontend/target/frontend-working-directory/node/node
>
> /<path>/nifi/nifi-frontend/target/frontend-working-directory/node_modules/nx/src/daemon/server/start.js
>

 If your seeing something you should be able to run npx nx reset from
*/<path>/nifi/nifi-frontend/target/frontend-working-directory*

On Thu, Oct 10, 2024 at 7:01 PM Mike Thomsen <mikerthom...@gmail.com> wrote:

> Matt,
>
> Yes, I think I built main about a week ago. Never seen it before. Yup, it's
> a hard blocker each time.
>
> mvn clean install -DskipTests=true
>
> I verified each node instance is dead w/ "killall -9 node" and "ps -ef |
> grep -i node"
>
> On Thu, Oct 10, 2024 at 4:40 PM Matt Gilman <matt.c.gil...@gmail.com>
> wrote:
>
> > Hey Mike,
> >
> > A couple questions...
> >
> > Have you been building regularly?
> > Does it usually complete without issue?
> > If you kill this one and try again, is this hanging repeatable?
> > What maven command did you run?
> > Is this a clean build with nothing in the target directories?
> >
> > The verbose flag is already set in the command front end build command.
> > There's likely some additional parameters [1] that could be specified
> there
> > to help track things down. I know we can drive the number of workers if
> > we're dealing with some sort of resource contention issue.
> >
> > [1] https://nx.dev/nx-api/nx/documents/run-many
> >
> > On Thu, Oct 10, 2024 at 4:10 PM Mike Thomsen <mikerthom...@gmail.com>
> > wrote:
> >
> > > I get to about this point, and it just hangs (seriously, 60 min in and
> > it's
> > > still not moving) on my Intel Mac:
> > >
> > > [INFO]
> > > [INFO] To address all issues, run:
> > > [INFO]   npm audit fix
> > > [INFO]
> > > [INFO] Run `npm audit` for details.
> > > [INFO]
> > > [INFO] --- frontend:1.15.0:npx (lint) @ nifi-frontend ---
> > > [INFO] Skipping execution.
> > > [INFO]
> > > [INFO] --- frontend:1.15.0:npx (package-web-ui) @ nifi-frontend ---
> > > [INFO] Running 'npx env-cmd -f .build.env nx run-many --verbose -t
> build'
> > > in
> > >
> > >
> >
> /Users/mikethomsen/workspace/nifi/nifi-frontend/target/frontend-working-directory
> > >
> > > Any ideas on how to get this build to be verbose in its output so I can
> > > figure out if it's running slowly or just hanging?
> > >
> >
>

Reply via email to