Skip to content

[BUG]: remove leading slash from version file name #4236

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 1 commit into from
Apr 9, 2025

Conversation

codetheweb
Copy link
Contributor

@codetheweb codetheweb commented Apr 8, 2025

Description of changes

Minio and S3 treat leading in keys differently. Minio strips the leading slash, S3 does not. This means that attempting to look up the key /foo for s3://sample-bucket/foo fails, but succeeds when testing locally with Minio.

This materializes as the garbage collector being unable to fetch version files in staging.

I will update the collections.version_file_name column in staging after merge to manually remove the leading slash.

Test plan

How are these changes tested?

I connected to the Postgres sysdb in my local environment and verified that version file names are now saved without a slash prefix.

Copy link

github-actions bot commented Apr 8, 2025

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

  • Can you think of any use case in which the code does not behave as intended? Have they been tested?
  • Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
  • If appropriate, are there adequate property based tests?
  • If appropriate, are there adequate unit tests?
  • Should any logging, debugging, tracing information be added or removed?
  • Are error messages user-friendly?
  • Have all documentation changes needed been made?
  • Have all non-obvious changes been commented?

System Compatibility

  • Are there any potential impacts on other parts of the system or backward compatibility?
  • Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

  • Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

@codetheweb codetheweb marked this pull request as ready for review April 9, 2025 00:00
@codetheweb codetheweb enabled auto-merge (squash) April 9, 2025 00:03
@codetheweb codetheweb merged commit 60e0b56 into main Apr 9, 2025
83 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants