Catch HTTP Error / 504 when pushing transaction
Opened this issue · 3 comments
https://github.com/grigio/eosfilestore/blob/master/src/core.ts#L35
Can fail with a 504 HTTP error and no attempt to retry is done thereby failing the upload all together. The upload/push tx should be tried again if the reason it failed is a non-resource (CPU/NET) reason.
Hi thanks for the report. Currently who does the transactions have to be sure to have enough resources to process them. NET is stable per tx but CPU depends on network congestion.
Retry currently isn't supported
Even with enough resources (NET/CPU) I have encountered 504 HTTP errors when testing uploading with "large" (~600kb) files, likely because the BP end point to push the transaction thinks I'm spamming, not the EOS network itself.
Currently the biggest file I've tried to upload successfully is 140kb, probably there are some limitations on eos BP apis