storage-resize-images: Add a retry option in case of operation failure
See original GitHub issueThis feature request is for extension: \storage-resize-images
What feature would you like to see?
Recently I’ve experienced a surge in storage “backend errors” that cause this function to often fail in its duty.
I would like to see an additional configuration option to set the maximum number of retries that should be performed should the extension function fail.
How would you use it?
I would use it to increase the reliability of the extension in times of great firebase storage turmoil and hopefully reduce the number of missing resized images.
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Retrying event-driven functions - Google Cloud
This causes the event to be retried repeatedly for up to multiple days until the function successfully completes. Warning: Setting "retry on failure"...
Read more >Retry Link - Apollo GraphQL Docs
Retry Link · Attempt an operation multiple times if it fails due to network or server errors. · Overview · Options · Avoiding...
Read more >Retry guidance for Azure services - Microsoft Learn
This guide summarizes the retry mechanism features for most Azure services, and includes information to help you use, adapt, or extend the retry...
Read more >Retry - Everything curl
Using the --retry option you can tell curl to retry certain failed transfers. ... The most aggressive form of retry is for the...
Read more >To retry a failed publication
Using the option to “Retry” failed instances of a publication, you can: ... process only the failed recipients, in case of a partial...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hey @jhuleatt, last week we discussed how this could be implemented.
retry: 1
.retry
prop will maintain count of retries and limit can be set by either us or user (to be decided).We already have an issue open for users who want to vote on whether to have a separate folder for images that have failed to resize https://github.com/firebase/extensions/issues/563. This could either replace or integrate with such a feature.
If any users would like to see this implemented, please leave a comment here 😄
Sounds like a great solution! I am assuming you would only retry as a catch all for any third party errors though e.g. storage api failures, correct? Bad image data for example should just be ignored.