Page MenuHomePhabricator

[services] Backup - Use Blob client in c++ - Implement add attachment
ClosedPublic

Authored by karol on Sep 1 2022, 4:10 AM.
Tags
None
Referenced Files
F3365803: D5018.id16355.diff
Mon, Nov 25, 7:49 AM
Unknown Object (File)
Fri, Nov 22, 1:51 AM
Unknown Object (File)
Wed, Nov 20, 8:17 PM
Unknown Object (File)
Tue, Nov 12, 7:54 AM
Unknown Object (File)
Mon, Nov 11, 11:55 AM
Unknown Object (File)
Sun, Nov 10, 6:57 AM
Unknown Object (File)
Sun, Nov 3, 2:47 AM
Unknown Object (File)
Tue, Oct 29, 4:22 PM

Details

Summary

Depends on D5017

Adding c++ implementation for using the blob client in the backup reactor for adding attachments.

Test Plan

backup builds

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

tomek requested changes to this revision.Sep 5 2022, 5:56 AM
tomek added inline comments.
services/backup/src/Reactors/server/AddAttachmentsUtility.cpp
78–80 ↗(On Diff #16246)

Doesn't seem like parentheses pair here.

backup builds

Are you sure?

This revision now requires changes to proceed.Sep 5 2022, 5:56 AM

fix

services/backup/src/Reactors/server/AddAttachmentsUtility.cpp
78–80 ↗(On Diff #16246)

ok thx not sure how this happened, will fix

remove the comments

tomek added inline comments.
services/backup/src/Reactors/server/AddAttachmentsUtility.cpp
81 ↗(On Diff #16396)

Is there a downside of calling one write after another without the read between them?

This revision is now accepted and ready to land.Sep 7 2022, 5:24 AM
services/backup/src/Reactors/server/AddAttachmentsUtility.cpp
81 ↗(On Diff #16396)

I think I explained this in another task. Anyway, the thing is, this is how grpc works, it yields a response even if it is empty. Our response queue is limited to 1 (after that, it will hang), so we should always read using the bidi stream, no matter if we use the response or not. We can, of course, add additional logic that would automatically discard responses.

This revision was landed with ongoing or failed builds.Sep 8 2022, 4:10 AM
This revision was automatically updated to reflect the committed changes.