Fix: preventing leading slash in S3/MinIO keys when prefix is empty#1902
Open
AadarshBhalerao wants to merge 1 commit intostrands-agents:mainfrom
Open
Fix: preventing leading slash in S3/MinIO keys when prefix is empty#1902AadarshBhalerao wants to merge 1 commit intostrands-agents:mainfrom
AadarshBhalerao wants to merge 1 commit intostrands-agents:mainfrom
Conversation
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.
Description
Fixes an issue where the S3 session manager fails when the prefix is empty.
Previously, an empty prefix caused incorrect handling during S3 session initialization.
This change ensures that empty prefixes are handled safely while maintaining existing behavior for valid prefixes.
Related Issues
Fixes #1863
Documentation PR
N/A
Type of Change
Bug fix
Testing
Tested locally by running the S3 session flow with:
Both scenarios now behave as expected.
hatch run prepareChecklist
This change is backward compatible and does not affect existing S3 prefix behavior.