fix: make tmp var global for EXIT trap access#13
Merged
davidristov merged 1 commit intomainfrom Mar 11, 2026
Merged
Conversation
krsh
approved these changes
Mar 11, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Running
curl -fsSL https://raw.githubusercontent.com/exein-io/analyzer-cli/main/dist/install.sh | bashinstalls the CLI properly but fails with/tmp/analyzer-install.sh: line 1: tmp: unbound variable.The issue is that
tmpis being set as local variable in main buttrap 'rm -rf "$tmp"' EXITfires after main returns at which pointtmpis out of scope. Combined withset -uwe get the error above.The fix is removing the declaration of
tmpas a local variable, in which case bash treats it as a global one and it is accessible when the EXIT trap runs.