Repository navigation
fix: remove orphaned duplicate ;; left over from Python 3.9 removal - #554
Merged
aavinash-nr merged 1 commit intoOct 12, 2026
Merged
Conversation
newrelic#552 removed the "python3.9") case arm from layer_name_str() in libBuild.sh but left its trailing ;; terminator behind, producing two consecutive ;; with no pattern before the second one. A bare ;; with no preceding case pattern is invalid bash syntax, so libBuild.sh fails to parse at all — breaking every runtime's build (not just Python's), since every publish-layers.sh sources this file before doing anything runtime-specific. Confirmed via bash -n: this was the only remaining instance of the pattern in the file, and no other python3.9 references remain anywhere in libBuild.sh.
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
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.
Summary
#552removed the"python3.9")case arm fromlayer_name_str()inlibBuild.shbut left its trailing;;terminator behind, producing two consecutive;;with no case pattern before the second one.;;with no preceding pattern is invalid bash syntax, solibBuild.shcurrently fails to parse at all onmaster— breaking every runtime's build (not just Python's), since everypublish-layers.shsources this file before doing anything runtime-specific.bash -n libBuild.sh: this was the only remaining instance of the pattern in the file, and no otherpython3.9references remain anywhere inlibBuild.sh.This is why the
v14.7.0.2_nodejstag's build failed with../libBuild.sh: line 103: syntax error near unexpected token;;'` — the same failure will hit the next release of any runtime until this merges.Test plan
bash -n libBuild.shpasses cleanly after the fix (verified locally)python3.9references remain inlibBuild.shpublish-*.ymltag push to confirm the Docker build'sRUN ./publish-layers.sh build-*step no longer fails at thesource ../libBuild.shstep