Draft
Conversation
This commit introduces an upload queue for failed storage operations and implements per-user storage usage tracking. It includes database schema changes, API modifications for the `/upload_file` endpoint, and new service functions for managing uploads and usage. Co-authored-by: markmhendrickson <[email protected]>
|
Cursor Agent can help with this pull request. Just |
Co-authored-by: markmhendrickson <[email protected]>
markmhendrickson
force-pushed
the
dev
branch
2 times, most recently
from
255d871 to
f6724f2
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.
Implement storage infrastructure with an upload retry queue and per-user usage tracking to improve ingestion resiliency and enable future quota enforcement.
The
upload_fileendpoint now handles transient Supabase Storage failures by enqueuing the upload for retry, returning a 202 status, rather than a 500. This ensures uploads eventually complete and provides a foundation for the async worker (FU-130) and strict quota enforcement (FU-136). Per-user storage and interpretation usage is also tracked via new database tables and functions.