Skip to content

fix(upload): send each file's original path with the upload request - #51

Open
bjay-wk wants to merge 1 commit into
mainfrom
fix/upload-original-file-path
Open

bjay-wk wants to merge 1 commit into
mainfrom
fix/upload-original-file-path

Conversation

@bjay-wk

@bjay-wk bjay-wk commented Oct 15, 2026

Copy link
Copy Markdown
Collaborator

Why

Tellers creates a project from an uploaded edit (.otio, .aaf, .edl, FCP7 .xml) by matching each clip's media against the user's assets on original_file_path: first the file name, then the folders above it to break ties (tellers_common/aaf_sequence.py, _name_matches / _resolve_one). The CLI never filled SourceFileInfo.original_file_path, so when an edit was uploaded after its media, none of the media was found and no project was created.

Change

build_single_upload_request now sets original_file_path to the canonical local path of each file. The backend already stores it (database/assets.py).

Test

  • cargo build --release and cargo test: 9 passed.
  • Pointed TELLERS_API_BASE at a local capture server and ran tellers upload upload <relative path>. POST /users/assets/upload_urls carried the absolute "original_file_path".
  • Not run against the real API.

Used by the transfer workflow in tellers-ai/tellers-skills (references/transfer-to-tellers.md).

🤖 Generated with Claude Code

Tellers matches the media of an uploaded edit (.otio, .aaf, .edl, FCP7 .xml)
against assets by original_file_path: the file name first, then the folders
above it. The CLI never set it, so an edit uploaded after its media found
none of it and was not converted into a project. Send the canonical local
path of every uploaded file.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.

1 participant