-
Notifications
You must be signed in to change notification settings - Fork 535
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
Image returning {} on about 2% of uploads #176
Comments
I believe its having an 'x' in the filename. |
Yes I can confirm having x in the filename returns {} |
We have updated our solution, and I believe your issue has been fixed. If you still see the issue with the latest version (v4.2), please feel free to reopen the issue. You can refer to the recent changes here |
@beomseoklee what is the best way to update on AWS? |
If you don't mind to create a new stack, it would be better to launch the new one. If you wish to keep your old one, I would say you can update the stack with the latest template, which is https://s3.amazonaws.com/solutions-reference/serverless-image-handler/latest/serverless-image-handler.template With the new template, I believe your Lambda function would be updated as well. |
I am not sure this was fixed entirely. I have the following examples: Works: Doesn't Work: |
@shortdoormedia Do you use the resizing? For example, |
@beomseoklee we have a unique scenario where we are transitioning from an old CDN to a new one and have a flat directory with files containing names like /test-100x100.jpg. They were linked to statically without any resizing method. What I have done is updated our lambda function to find a request uri without resizing and a path with dimensions and applying that as the fit-in. Deploying now to see if it works:
Edit fix errors and formatting x 20 times |
On about 2% of the images I upload to the s3 the cloudFront url returns {} instead of an image.
Any clues on how to fix this?
The text was updated successfully, but these errors were encountered: