Fix large image upload with S3 assetstore #835
+24
−3
Conversation
This file contains 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
The getTiles API from large_image expects the field large_image to be set when recovering the tiles, but due to the S3 assetstore, that field can take a bit of time to be set. Retry that function a few times (10) if it fails to wait for that field to be set.
|
Tested on prod, it indeed fixes the issue: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The getTiles API from large_image expects the field large_image to be set when recovering the tiles, but due to the S3 assetstore, that field can take a bit of time to be set.
Retry that function a few times (10) if it fails to wait for that field to be set.