-
-
Notifications
You must be signed in to change notification settings - Fork 29
[#3113] Reconciled the drifted duplicate helpers across the shipped tooling scripts. #3124
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
Merged
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
fd6aac3
[#3113] Converged the 'extract_json_*' copies onto one quoted form.
AlexSkrypnyk b005b8c
[#3113] Placed the 'drush()' wrapper with the other definitions.
AlexSkrypnyk 8e4ec68
[#3113] Restored the boilerplate 'task()' and 'pass()' to the shipped…
AlexSkrypnyk d0038f8
[#3113] Promoted the Acquia API error checks into the task scripts.
AlexSkrypnyk a6917f0
[#3113] Converged the Lagoon CLI flags and the command availability c…
AlexSkrypnyk 996b6d2
[#3113] Extracted the repeated override-database block in the Lagoon …
AlexSkrypnyk 8eb8a10
[#3113] Covered the Acquia copy tasks and the Lagoon custom task with…
AlexSkrypnyk 6bd70ac
[#3113] Moved the override flag rationale into the function docblock.
AlexSkrypnyk e0f2cec
[#3113] Covered both missing environment branches in the Acquia copy …
AlexSkrypnyk 5cc5d15
Addressed code review: strengthened the Acquia task test assertions a…
AlexSkrypnyk d858736
[#3113] Reverted the Lagoon deploy extraction and the boilerplate hel…
AlexSkrypnyk File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: drevops/vortex
Length of output: 226
🤖 get_repo_knowledge executed:
get_repo_knowledge drevops/vortex /tmp/coderabbit-repo-knowledge/drevops-vortex-95aed43f/learnings /tmp/coderabbit-repo-knowledge/drevops-vortex-95aed43f/conventionsLength of output: 28378
🏁 Script executed:
Repository: drevops/vortex
Length of output: 11273
🏁 Script executed:
Repository: drevops/vortex
Length of output: 11225
Encode UTF-8 bytes in
uri_encode_key.In a UTF-8 locale,
${_s:0:1}processeséas one character, soprintfemits%E9. AWS SigV4 requires the UTF-8 bytes%C3%A9. S3 uploads with non-ASCIIVORTEX_PUSH_DB_S3_PREFIXorVORTEX_PUSH_DB_S3_REMOTE_FILEcan target the wrong key or fail.Set the function-local locale to
Cand add a BATS case for a UTF-8 object key.Proposed fix
uri_encode_key() { + local LC_ALL=C _s="${1}"🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The analysis is correct - in a UTF-8 locale ${_s:0:1} takes a character rather than a byte, so a non-ASCII object key percent-encodes to the wrong bytes for SigV4.
Not adopted here, because uri_encode_key is not changed by this PR. Its body is byte-identical to main; the diff only moves the function up to sit with the other definitions, which is the placement convention this PR is establishing. A locale fix plus the UTF-8 BATS case is a correctness change to S3 key encoding and deserves its own issue and review rather than riding along in a de-duplication PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AlexSkrypnyk, understood. The finding is valid, but the change is outside this PR’s helper-placement scope.Would you like me to open a follow-up GitHub issue for the
uri_encode_key()locale fix and UTF-8 BATS coverage?🐇
✏️ Learnings added
You are interacting with an AI system.