-
-
Notifications
You must be signed in to change notification settings - Fork 402
Replies: 2 comments · 4 replies
-
some sort of race condition, possibly with file locks. enabling trace logging may help. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Thank you for the hint. Even with tracing enabled I'm not sure I can properly make any sense out of the output. I found a better way to reproduce it btw:
And then in two different terminals you execute it in the loop. In one terminal you enable export MISE_TRACE=1
for i in $(seq 1 2000); do mise example $i; done
|
Beta Was this translation helpful? Give feedback.
All reactions
-
Sorry, I totally forgot to mention version etc:
|
Beta Was this translation helpful? Give feedback.
All reactions
-
#!/usr/bin/env bash
set -eou pipefail
echo $1 for i in $(seq 1 2000); do mise example $i; done Even that sometimes hangs, without having a 2nd process of |
Beta Was this translation helpful? Give feedback.
All reactions
-
@jdx does it make sense to create an issue for this one? |
Beta Was this translation helpful? Give feedback.
All reactions
-
I reported this as well #4127 What we found is that if ANY tool is not installed in any of the configs mise was using, it could trigger the hang. We "fixed" this on CI by making sure we were excluding all asdf config files that were present on the cloud machines as well as excluding any specific tools it would try to identify that we did not intend to install. While it worked to keep things moving, definitely doesn't address the root cause, but hopefully provides some help as to where to look. |
Beta Was this translation helpful? Give feedback.
-
We've seen this happen on CI sometimes, but I also found a way to trigger it:
mise-tasks/example
Execute:
The strange thing is, that the whole invocation of
22
in this case is missing. So it didn't printstart 22
, neitherdone 22
.Any idea what this might be?
Beta Was this translation helpful? Give feedback.
All reactions