Page MenuHomePhabricator

[lib] Stop processing user infos from secondary keyservers on keyserverAuthActionTypes
ClosedPublic

Authored by inka on Jun 6 2024, 6:43 AM.
Tags
None
Referenced Files
F3496776: D12332.diff
Thu, Dec 19, 2:52 PM
F3495716: D12332.id41685.diff
Thu, Dec 19, 9:44 AM
F3495715: D12332.id41102.diff
Thu, Dec 19, 9:44 AM
F3495714: D12332.id41046.diff
Thu, Dec 19, 9:44 AM
F3495707: D12332.id.diff
Thu, Dec 19, 9:44 AM
F3495706: D12332.diff
Thu, Dec 19, 9:44 AM
Unknown Object (File)
Tue, Dec 10, 9:36 PM
Unknown Object (File)
Mon, Dec 9, 4:45 PM
Subscribers

Details

Summary

issue: ENG-7832

Test Plan

Checked that user infos from auth keyserver are still being persisted on keyserverAuthActionTypes
EDIT: verified that when connecting to a secondary keyserver no errors appear.

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

inka requested review of this revision.Jun 6 2024, 6:59 AM
tomek requested changes to this revision.Jun 6 2024, 9:53 AM
tomek added inline comments.
lib/actions/user-actions.js
622–623 ↗(On Diff #41046)

I don't think it is guaranteed that there will always be a response from the authoritative keyserver, e.g. when adding a new keyserver. We probably should add a condition here and extend a test plan to verify a non-auth keyserver auth.

This revision now requires changes to proceed.Jun 6 2024, 9:53 AM

Check if response from auth keyserver exists

This revision is now accepted and ready to land.Jun 7 2024, 6:49 AM