reth-entrypoint: use safe parameter expansion to prevent set -u unbound variable errors #529
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.
Reason: With set -u, referencing unset variables in conditions (e.g., [[ -z "$RETH_CHAIN" ]] and checking RETH_FB_WEBSOCKET_URL) causes an “unbound variable” error, terminating the script unexpectedly.
Change: Updated conditional checks to use safe expansion ${RETH_CHAIN:-} and ${RETH_FB_WEBSOCKET_URL:-}.
Goal: Prevent crashes when optional env vars are unset while preserving existing behavior when they are provided.