Open CluEleSsUK opened 1 week ago
Also since updating everything to 1.29.4 I’ve been getting occasional core dumps from tokio which seems suspicious:
RUN moon docker scaffold some-module
client-js:integration | 1.175 ▪▪▪▪ installing proto 0.42.0
client-js:integration | 8.001 ▪▪▪▪ installing node 22.3.0
client-js:integration | 1171.8
client-js:integration | 1171.8 thread 'tokio-runtime-worker' has overflowed its stack
client-js:integration | 1171.8 fatal runtime error: stack overflow
client-js:integration | 1172.7 Aborted (core dumped)
update on this one: seems I had a circular dependsOn
in my moon files :| though weirdly moon ci
works fine for this. Is it worth raising a separate issue for docker scaffold allowing to start with circular dependencies?
@CluEleSsUK Is the cycle the problem for the original post? If so, you can edit the post/title to mention the cycle instead and I can look into it.
No, cycle is just for the tokio stack overflow
I don't see anything in the diff that would cause this: https://github.com/moonrepo/moon/compare/7d3702984e9774e2dc0a9d42d49977fd165585e1..ac8fa57f2b35b746e16df6d756fc44e74bbd64fe
Did npm install
run and succeed? The error seems like @moonrepo/cli
wasn't installed into node modules correctly.
Describe the bug
There appears to be an incompatibilty in the docker setup step of 1.29.4
In my package.json devDependencies I have
^1.29.3
. Locally I'm running1.29.2
Inside my dockerfile I curlpipebash the latest version (1.29.4
at present) when runningRUN moon docker setup
in my dockerfile, I get the following error:Expected behavior
It could be that the docker packages move around, but I wouldn't expect a patch upgrade to break compat
Screenshots
Environment
Additional context