-
Notifications
You must be signed in to change notification settings - Fork 448
Client::WriteObject() still raises errors in some cases. #2374
Copy link
Copy link
Closed
Labels
api: storageIssues related to the Cloud Storage API.Issues related to the Cloud Storage API.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Milestone
Metadata
Metadata
Assignees
Labels
api: storageIssues related to the Cloud Storage API.Issues related to the Cloud Storage API.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
In most cases
Client::WriteObject()signals errors by setting the iostream status bits and the.status()accessor in the returnedObjectWriteStream. But if the error condition is detected before we even create a validObjectWriteStreambufthen the function raises an exception.That is not the expected behavior.