BUG: Remove source set-env and run it manually #64
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.
As we run the shell script bootstrap.sh in a dedicated bash process and vars that we export also die with the process getting reaped. Because we also "set -euo pipefail" in bootstrap we cannot get the user to "source" the env, else any failing command from that point will close their session.
Update the docs to manually get the user to run
source set-env.sh, and drop setting exit on pipefail to avoid killing the user's session.Accompanying diff for our docs: https://stfc.atlassian.net/wiki/pages/diffpagesbyversion.action?pageId=211878034&selectedPageVersions=64&selectedPageVersions=65