Page MenuHomePhabricator

[services] Backup - Apply reading user id in the reactors
ClosedPublic

Authored by karol on Mar 29 2022, 4:38 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Jun 30, 7:28 PM
Unknown Object (File)
Sun, Jun 30, 12:07 PM
Unknown Object (File)
Sun, Jun 30, 12:07 PM
Unknown Object (File)
Sun, Jun 30, 12:07 PM
Unknown Object (File)
Sun, Jun 30, 12:07 PM
Unknown Object (File)
Sun, Jun 30, 12:04 PM
Unknown Object (File)
Sat, Jun 29, 1:56 PM
Unknown Object (File)
Fri, Jun 28, 3:11 PM

Details

Summary

Depends on D3530

In the previous diff, I added a user id for every request where it was missing. Now, we want to read it when creating a new backup and sending a log.

Test Plan
cd services
yarn run-backup-service

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

karol edited the test plan for this revision. (Show Details)
karol added reviewers: tomek, max, varun, jim.
karol edited the summary of this revision. (Show Details)
Harbormaster returned this revision to the author for changes because remote builds failed.Mar 29 2022, 4:53 AM
Harbormaster failed remote builds in B7668: Diff 10764!
tomek requested changes to this revision.Mar 31 2022, 9:46 AM
tomek added inline comments.
services/backup/docker-server/contents/server/src/Reactors/server/SendLogReactor.h
38 ↗(On Diff #10764)

This can be removed

48–54 ↗(On Diff #10764)

This code should be introduced before this diff. Is it a mistake due to rebasing?

This revision now requires changes to proceed.Mar 31 2022, 9:46 AM

strip added code(adding it in the next diff), remove comment

services/backup/docker-server/contents/server/src/Reactors/server/SendLogReactor.h
38 ↗(On Diff #10764)

right

48–54 ↗(On Diff #10764)

Uhm, maybe...
Added in D3612

This revision is now accepted and ready to land.Apr 5 2022, 9:20 AM
services/backup/docker-server/contents/server/src/Reactors/server/CreateNewBackupReactor.h
67

I still find it weird that we have a separate trip for each field. I know we have a task out for this but would be great to prioritize it