fix(cache): fix incorrect S3 url composition when S3_ENDPOINT is set#9550
Merged
cschmatzler merged 1 commit intotuist:mainfrom Feb 20, 2026
Merged
Conversation
dosubot
bot
added
size:M
|
Related Documentation Checked 1 published document(s) in 1 knowledge base(s). No updates required. How did I do? Any feedback? |
cschmatzler
commented
Feb 20, 2026
Member
Author
cschmatzler
left a comment
cschmatzler
left a comment
There was a problem hiding this comment.
Also needs a quick mix format in the cache/ directory to make CI pass :)
yusufozgul
force-pushed
the
fix/CacheS3OperationError
branch
from
4575d30 to
c95f717
Compare
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
2 participants
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.
When
S3_ENDPOINTwas set,runtime.exswould incorrectly concatenate parsedhostandportinstead of keeping them two separate configuration items for ex_aws.