Page MenuHomePhabricator

[DRAFT] [services] Backup - Connect to Blob - add error messages for async errors
AbandonedPublic

Authored by karol on Aug 24 2022, 5:56 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Dec 13, 1:09 AM
Unknown Object (File)
Fri, Nov 29, 1:15 AM
Unknown Object (File)
Nov 10 2024, 9:35 PM
Unknown Object (File)
Nov 10 2024, 6:58 AM
Unknown Object (File)
Oct 27 2024, 8:11 PM
Unknown Object (File)
Oct 27 2024, 8:11 PM
Unknown Object (File)
Oct 27 2024, 8:09 PM
Unknown Object (File)
Oct 25 2024, 6:17 AM

Details

Summary

Depends on D4943

I didn't know how to properly handle errors in the async blocks so I just added a collection to gather them.

@varun any better ideas?

Test Plan

Test plan in D4946

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

karol retitled this revision from [services] Backup - Connect to Blob - add error messages for async errors to [DRAFT] [services] Backup - Connect to Blob - add error messages for async errors.Aug 24 2022, 6:03 AM
karol edited the summary of this revision. (Show Details)
karol edited the test plan for this revision. (Show Details)
karol added reviewers: varun, tomek.
karol added a subscriber: varun.
tomek requested changes to this revision.Aug 29 2022, 4:38 AM

Not sure how these functions will be used, but I guess if an error occurs, we can just stop the execution of a method and set a value in future.

services/backup/blob_client/src/put_client.rs
56–63
  1. We don't need to use an explicit return as a last statement
  2. We should avoid mutable variables
This revision now requires changes to proceed.Aug 29 2022, 4:38 AM
services/backup/blob_client/src/put_client.rs
56–63

ok

Abandoning this stack in favor of the new one that starts @ D5002.

All the comments have been either addressed inline or in the new stack.