fix: cap Pexels b-roll at 1080p to prevent Lambda disk overflow#621
Merged
codercatdev merged 1 commit intodevfrom Mar 5, 2026
Merged
fix: cap Pexels b-roll at 1080p to prevent Lambda disk overflow#621codercatdev merged 1 commit intodevfrom
codercatdev merged 1 commit intodevfrom
Conversation
selectBestFile() was falling back to the highest resolution file when no exact 1080p match existed. This selected 4K UHD files (4096×2160, 100-500MB) that exceeded Lambda's 2GB disk limit, causing all render chunks to fail. Now prefers the highest resolution at or below 1080p. If all files exceed 1080p, picks the smallest available instead of the largest.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
codercatdev
added a commit
that referenced
this pull request
Mar 5, 2026
fix: cap Pexels b-roll at 1080p — Lambda disk overflow fix
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
1 participant
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.
Fix: Cap Pexels B-Roll at 1080p
Root cause:
selectBestFile()inpexels.tswas falling back to the highest resolution file when no exact 1080p match existed. This selected 4K UHD files (4096×2160, typically 100-500MB) that exceeded Lambda's 2GB disk limit, causing all 91 render chunks to fail with disk space errors.Fix: Changed the fallback logic in
selectBestFile():One file changed:
lib/services/pexels.ts— only theselectBestFile()function.The selection priority is now:
No other files changed. The
getBRollForScene()andsearchVideos()APIs are unchanged.