-
Notifications
You must be signed in to change notification settings - Fork 4.4k
fix(producer): mix audio into a container that can record encoder delay #3200
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
Changes from 2 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
fbfaa75
fix(producer): mix audio into a container that can record encoder delay
miguel-heygen 927f44e
fix(cloud): read the plan audio artifact name from the producer contract
miguel-heygen c171e1c
fix(cloud): accept a legacy plan's audio artifact name for one release
miguel-heygen 4d8eb93
test(producer): rebake the missing-host-comp-id golden without the au…
miguel-heygen 5f7ef6d
test(producer): rebake the variables-prod golden without the audio delay
miguel-heygen File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟠 Backward-compat concern — plan-writer/assembler mixed-version window
Miguel raised this himself in the PR body ("a plan written by an older build would not be found by a newer assembler"). This is the primary read site for the S3 v1 assemble path, and I think the window IS reachable given the plan-store-and-forward shape here — the plan is uploaded to S3 as a tarball, and there's no coordination that forbids a NEWER
handleAssemblefrom picking up a plan tarball whoseaudio.aacwas written by the pre-fix build (in-flight batches during a deploy, replay-on-failure of an older event, cross-region propagation lag, whatever). When that happens,existsSync(join(planDir, PLAN_AUDIO_RELATIVE_PATH))at the sibling v2 site (:622-624) isfalse,handleAssemblehere reads a non-existent path and the assembler proceeds without audio — silent no-audio render, not a loud failure.A one-release compat window closes it cheaply. Something like:
Or, for the S3 v1 path here, just OR the legacy name into the existing branch. Same treatment needed at:
handler.ts:622-624(S3 v2 assemble)packages/gcp-cloud-run/src/server.ts:571-577(GCS v1)packages/gcp-cloud-run/src/server.ts:622-624(GCS v2)Delete the legacy name in the next release. If the plan-store-and-forward mixed-version window ISN'T reachable in practice (all planners + assemblers deploy atomically together, no in-flight replay of older plans), then this reduces to a no-op comment saying so. Either resolution is fine — the current state (no fallback, no note documenting the reasoning) is what leaves someone else in the dark on the deploy day.
— Rames D Jusso