You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did sugar launch to launch my NFT collection of size of around 5 GB to upload on AWS, but it got operation timed out for around 100 times, although uploading starts from where it was left. but say If i upload the assets files on S3 bucket and starts sugar launch, then sugar just checks if it is uploaded already then create a cache file that's it. If not uploaded then it uploads !
Ideal solution or implementation
In aws.rs, we can add some sort of tracking system that tracks if current file that's going for a upload is already there or not.
Alternative solutions or implementations
No response
Other context
No response
The text was updated successfully, but these errors were encountered:
Feature
I did sugar launch to launch my NFT collection of size of around 5 GB to upload on AWS, but it got operation timed out for around 100 times, although uploading starts from where it was left. but say If i upload the assets files on S3 bucket and starts sugar launch, then sugar just checks if it is uploaded already then create a cache file that's it. If not uploaded then it uploads !
Ideal solution or implementation
In aws.rs, we can add some sort of tracking system that tracks if current file that's going for a upload is already there or not.
Alternative solutions or implementations
No response
Other context
No response
The text was updated successfully, but these errors were encountered: