Page MenuHomePhabricator

[identity] fix `lastPrimarySignature` attribute
ClosedPublic

Authored by kamil on Thu, Dec 5, 3:59 AM.
Tags
None
Referenced Files
F3504978: D14079.id46215.diff
Fri, Dec 20, 11:43 AM
F3504943: D14079.id46229.diff
Fri, Dec 20, 11:25 AM
F3503736: D14079.diff
Fri, Dec 20, 6:22 AM
Unknown Object (File)
Wed, Dec 18, 5:00 AM
Unknown Object (File)
Sun, Dec 15, 4:42 AM
Unknown Object (File)
Sun, Dec 15, 3:46 AM
Unknown Object (File)
Sun, Dec 15, 2:53 AM
Unknown Object (File)
Fri, Dec 13, 12:06 AM
Subscribers

Details

Summary

While testing restore flow, I discovered device list validation on other clients is not passing, it's because we don't store lastPrimarySignature in DDB correctly.

Test Plan

N/A, just carefully reading code - I am going to test this with actual restore after deploying on staging

Diff Detail

Repository
rCOMM Comm
Branch
restore
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

kamil held this revision as a draft.
kamil published this revision for review.Thu, Dec 5, 4:01 AM
This revision is now accepted and ready to land.Fri, Dec 6, 1:44 AM

How serious is this issue? Wondering what the product impact was, if any

How serious is this issue? Wondering what the product impact was, if any

I think there wasn't any product impact, the first time we used this was during restore protocol, and I added it later in this stack (D14083), I don't think any existing logic depends on this, but perhaps @bartek has a better view on this.

How serious is this issue? Wondering what the product impact was, if any

I think there wasn't any product impact, the first time we used this was during restore protocol, and I added it later in this stack (D14083), I don't think any existing logic depends on this, but perhaps @bartek has a better view on this.

There was no impact, this signature wasn't used anywhere before D14083