Check if cli exists before executing #237
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: pat-trunk-io <pat@trunk.io>
|
🚫 This pull request was closed by @pat-trunk-io, so it was removed from the merge queue. See more details here. |
gnalh
reviewed
Dec 14, 2024
|
I mean then it's a bit of a Heisenberg bug. If we observe it we can't reproduce, but if we don't observe it will happen. Fwiw, what I'm trying to figure is "what" is missing here. Exit code 127 means an executable was missing, but is it the analytic cli or something that it calls? |
|
The failure happened when running nextest. It doesn't seem to be a missing cli. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Check if CLI exists before executing.
We have seen some sporadic exit code 127.
https://trunk-io.slack.com/archives/C044VBASZ0D/p1734148787307919?thread_ts=1734148787.307919&cid=C044VBASZ0D