-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upload Retry Object not created #169
Comments
What does str(upload_try) return? That object should be a class object you use in the second attempt. |
Thanks so much for the quick response! The error message for I also tried to manually complete gcs_retry_upload by providing the upload_url, file and type but I got this error instead:
|
Hmm ok that's odd, it should return something. It's always been hard to test this one without a way to trigger a failed upload. |
Yeah it’s hard to create a reproducible example. Is there a way I can create a retry object without relying on the gcs_upload 3rd attempt failure? |
Hi! Writing to +1 this issue, I've just run into the same problem when trying to upload a 5.7MB file (painfully close to the upload limit). I also noticed that adjusting the upload limit didn't change the behavior (I tried to adjust the upload limit up to 10MBs to no avail). Again, hard to reproduce, but I'm having the same issue where the |
The upload limit should get you around it, can I see some code? Perhaps the option is not being applied. |
I'm trying to upload a large (1.5 Gb) file using gcs_upload(), and am following your instructions in the library vignette as follows:
I get an error as following, but
upload_try
is not saved as a retry object. In fact,upload_try
is not saved as an object at all.Therefore there's no retry object for me to enter into
gcs_retry_upload(upload_try)
. Is there anything else I can do to create a retry object?FWIW, I can access the GCS bucket fine to read and write smaller objects. It's just with large files which require a resumable upload when this code breaks.
The text was updated successfully, but these errors were encountered: