Go client lambda response update#2462
Merged
JonnyBurger merged 2 commits intoremotion-dev:mainfrom Jul 2, 2023
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Member
|
Oh, very well spotted! Thanks a lot for fixing this. |
|
🎉🎈 @alexfernandez803 has been awarded $50! 🎈🎊 |
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.
I've noticed that the lambda response signature, maybe related to the aws-lambda-go package update.
This MR fixes this issue and including update of example. Version is also added in getting progress values to prevent this issue
{"errorType":"Error","errorMessage":"Version mismatch: When calling getRenderProgress(), you called the function remotion-render-3-3-101-mem2048mb-disk2048mb-240sec which has the version 3.3.101 but the @remotion/lambda package is an older version. Deploy a new function and use it to call getRenderProgress(). See: https://www.remotion.dev/docs/lambda/upgrading","trace":["Error: Version mismatch: When calling getRenderProgress(), you called the function remotion-render-3-3-101-mem2048mb-disk2048mb-240sec which has the version 3.3.101 but the @remotion/lambda package is an older version. Deploy a new function and use it to call getRenderProgress().