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
UploadManager.upload_stream() raises MultipartUploadError when a timeout is set on the underlying object storage client, and the operation takes more than the read timeout to complete. Prior to v2.23.2, we were overwriting the timeout to None in the operations (please see known issues). The default timeout is a read timeout of 60 seconds, hence this scenario will be triggered by default in v2.23.2 on any use of this operation where the operation takes 60 or more seconds to complete.
We are actively working on a fix for this issue. In the mean time, you can work around the issue by explicitly setting the timeout to None. For example,
client.base_client.timeout = None
We apologize for any inconvenience this issue may cause you. We are working to promptly resolve this issue. Please stay tuned and watch this GitHub issue for updates.
The text was updated successfully, but these errors were encountered:
Update: This issue has been fixed in oci v2.23.3
UploadManager.upload_stream() raises
MultipartUploadError
when a timeout is set on the underlying object storage client, and the operation takes more than the read timeout to complete. Prior to v2.23.2, we were overwriting the timeout to None in the operations (please see known issues). The default timeout is a read timeout of 60 seconds, hence this scenario will be triggered by default in v2.23.2 on any use of this operation where the operation takes 60 or more seconds to complete.We are actively working on a fix for this issue. In the mean time, you can work around the issue by explicitly setting the timeout to None. For example,
client.base_client.timeout = None
We apologize for any inconvenience this issue may cause you. We are working to promptly resolve this issue. Please stay tuned and watch this GitHub issue for updates.
The text was updated successfully, but these errors were encountered: