spheronFdn / beta-testing

🐛 Report all the bug found during beta testing
4 stars 3 forks source link

UX bug: Retry creating transactions #15

Open tinybigideas opened 2 years ago

tinybigideas commented 2 years ago

Describe the bug

If a transaction creation were to fail, there doesn't seem to be a simple way to retry. In my case, a single image failed to be created which results in a broken state. I uploaded a simple html website so no reason for anything to fail.

Criticality

Low

To Reproduce

  1. Deploy site using Arweave
  2. Transaction failed for a single image

Not sure how to reproduce, just seen this pop up. More of a UX request than a bug.

Broken image link: https://x4gaoar2fxgsieib2qw4knnxhcnlrnpqaaeib27qwkvqvhvpui.arweave.net/vwwHAjotzSQRAdQtxTW3OJq4tfAACIDr8LK-rCp6voo/play

Expected behavior

A retry button for resources which fail, or a retry all button. I assume if I redeploy the entire thing, it'll retry, but a simple button here would suffice.

Screenshots

image

Desktop (please complete the following information):

Additional context

The image which failed is 2.66KB, added below:

image

No reason to fail as far as I see. Random occurance.

Your Details

tinybigideas commented 2 years ago

Ran full redeployment, and again, a single image failed. Although, this time the image was 499KB in size:

image

As to why only a single resource has failed twice in a row is odd. Will continue playing.

Deployed site: https://tb6kimtymznsftftwaxzgwaudyueqg4wvv2qafueggfh3f7u.arweave.net/mHykMn_hmWyLMs_7Avk1gUHi-hIG5atdQAWhDGKfZf0/things

Broken image link: https://tb6kimtymznsftftwaxzgwaudyueqg4wvv2qafueggfh3f7u.arweave.net/mHykMn_hmWyLMs_7Avk1gUHi-hIG5atdQAWhDGKfZf0/images/marlow_full.png

rekpero commented 2 years ago

This is happening due to high congestion on the arweave gateway. To resolve this, we are spinning up our own dedicated arweave gateway.

Also, there is no option to build the retry single file upload option as once the manifest is created after the deployment, it's not editable anymore.

Thanks @tinybigideas for reporting this