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
In the live stream with Steve Builds episode 3, the upload stopped without any error messages or anything. The upload was very slow and then he cancelled it after about 17 minutes. The estimated time was no longer going down, but stayed at around 1:30 minutes remaining. Running the same operation with a faster USB drive showed that it worked well.
It could be that the drive ran out of disk space for some reason. Although there should be a check for that, so that is not as likely. Perhaps there was a disruption that caused a chunk to fail for some reason and just continuing without giving an error message.
The text was updated successfully, but these errors were encountered:
Sometimes the "upload chunk" gets a timeout. Normally a an upload takes about 1.4 seconds, but it can be as long as 36 seconds in at least one instance. There is no "catch" on the upload requests that can be used to inform the user that something has gone wrong. At the very least, the error should be caught and an error message presented to the user.
In the live stream with Steve Builds episode 3, the upload stopped without any error messages or anything. The upload was very slow and then he cancelled it after about 17 minutes. The estimated time was no longer going down, but stayed at around 1:30 minutes remaining. Running the same operation with a faster USB drive showed that it worked well.
It could be that the drive ran out of disk space for some reason. Although there should be a check for that, so that is not as likely. Perhaps there was a disruption that caused a chunk to fail for some reason and just continuing without giving an error message.
The text was updated successfully, but these errors were encountered: