Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lerna incompatible with entr #4116

Open
kirrg001 opened this issue Nov 11, 2024 · 3 comments
Open

Lerna incompatible with entr #4116

kirrg001 opened this issue Nov 11, 2024 · 3 comments

Comments

@kirrg001
Copy link

Current Behavior

entr was working fine with Lerna v6. We have switched from Lerna v6 to v8.

Now we are getting a Node native error when running our tests with fd -e js -e mjs | entr run-tests.sh:

run-tests.sh
lerna notice cli v8.1.8

  #  /.nvm/versions/node/v20.13.1/bin/node[2162]: void node::PlatformInit(ProcessInitializationFlags::Flags) at ../src/node.cc:621
  #  Assertion failed: (err) == (0)

----- Native stack trace -----

 1: 0x1083d67e6 node::Assert(node::AssertionInfo const&) [/.nvm/versions/node/v20.13.1/bin/node]

  #  /.nvm/versions/node/v20.13.1/bin/node[2164]: void node::PlatformInit(ProcessInitializationFlags::Flags) at ../src/node.cc:621
  #  Assertion failed: (err) == (0)

----- Native stack trace -----

This worked fine on Lerna v6.

Expected Behavior

No error.

Steps to Reproduce

fd -e js -e mjs | entr run-tests.sh

run-tests.sh

#!/usr/bin/env bash
npx lerna exec "echo Hello" --scope=your-package-scope

I have tried using --max-buffer or --concurrency without success.
Verbose logs also don't contain any information.

lerna notice cli v8.1.8
lerna verb packageConfigs Explicit "packages" configuration found in lerna.json. Resolving packages using the configured glob(s): ["packages/*"]
lerna verb rootPath /dev/instana/nodejs

Alternative

Use watchexec -r.
Switch to mocha --watch (preferred).

Environment

Darwin x86 and M1/M3.
Tested multiple Node versions.

@JamesHenry
Copy link
Member

@kirrg001 Please retry with the latest, some important internals were upgraded between 8.1.8 and 8.1.9

@JamesHenry JamesHenry added the blocked: retry with latest Retry with latest release label Nov 12, 2024
@kirrg001
Copy link
Author

Thanks for your reply.

I have tried 8.1.9.
I have tried 8.0.2.

Did not work.

@JamesHenry
Copy link
Member

Ok thanks @kirrg001 sorry to hear it hasn't helped.

I am not familiar with the tooling you have mentioned, and I will please need your help to dig any further.

Please provide a minimal reproduction repo that we can both access that demonstrates the problem.

Thank you!

@JamesHenry JamesHenry added blocked: repro needed and removed blocked: retry with latest Retry with latest release labels Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants