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

fix(foundryup): actually make set -e work #6352

Merged
merged 2 commits into from
Nov 18, 2023
Merged

Conversation

DaniPopes
Copy link
Member

Motivation

Fixes #6329

TIL that using || on a function disables the global set -e for the function. lol.

5:18
https://youtu.be/30YWsGDr8mA?si=FfN-Fdbadxu_yJnZ&t=318

Solution

Copy link
Member

@Evalir Evalir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh wow, TIL!

@DaniPopes DaniPopes merged commit 138ab40 into master Nov 18, 2023
1 of 6 checks passed
@DaniPopes DaniPopes deleted the dani/foundryup-fail branch November 18, 2023 18:56
@warrickwicket
Copy link

This is a breaking change. foundryup now returns 1 if FOUNDRY_BIN_DIR is not in the PATH, which is not unreasonable for CI setups. I think it might make sense to relax this requirement.

@DaniPopes
Copy link
Member Author

DaniPopes commented Nov 20, 2023

How would foundryup fail if FOUNDRY_BIN_DIR is not in PATH? Can you please open an issue

@warrickwicket
Copy link

which EXECUTABLE returns 1, and that terminates the script with 1. I'll open a more detailed issue

@imulmat4
Copy link

Any chance we could revert this change? Not sure this exit is giving a ton of value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

foundryup does not properly exit on errors in piped commands
4 participants