Skip to content

gcsstore: Do not write info when loading info object#1300

Merged
Acconut merged 2 commits intotus:mainfrom
fetlife:gcs-storage-do-not-overwrite-info
Feb 21, 2026
Merged

gcsstore: Do not write info when loading info object#1300
Acconut merged 2 commits intotus:mainfrom
fetlife:gcs-storage-do-not-overwrite-info

Conversation

@Antti
Copy link
Copy Markdown
Contributor

@Antti Antti commented Aug 4, 2025

I didn't find the reason why is it writing back to info file when reading info (S3 storage is not doing it)

Fixes #343

kamze-wave added a commit to wavemm/tusd that referenced this pull request Feb 10, 2026
This is a backport of tus#1300 on top of tag v2.8.0
Signed-off-by: Kamil Zegier <kamil.zegier@wave.com>
@kamze-wave
Copy link
Copy Markdown

@Acconut can this PR be merged? I can confirm it has fixed our rate limit problem with GCP. We are now running a forked version with this change backported.

Copy link
Copy Markdown
Member

@Acconut Acconut left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thank you!

@Acconut Acconut changed the title GCS storage: Do not write info on getInfo gcssotre: Do not write info when loading info object Feb 21, 2026
@Acconut Acconut merged commit a022d19 into tus:main Feb 21, 2026
7 checks passed
@Antti Antti changed the title gcssotre: Do not write info when loading info object gcsstore: Do not write info when loading info object Mar 6, 2026
@Antti Antti deleted the gcs-storage-do-not-overwrite-info branch March 6, 2026 09:41
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.

GCS Rate limit exceeded.

3 participants