Page MenuHomePhabricator

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

Authored by inka on Thu, Jun 6, 6:43 AM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Jul 2, 12:41 AM
Unknown Object (File)
Mon, Jul 1, 11:52 PM
Unknown Object (File)
Mon, Jul 1, 1:47 PM
Unknown Object (File)
Sun, Jun 30, 9:04 PM
Unknown Object (File)
Sun, Jun 30, 9:28 AM
Unknown Object (File)
Sun, Jun 30, 1:54 AM
Unknown Object (File)
Sun, Jun 30, 1:41 AM
Unknown Object (File)
Tue, Jun 25, 10:37 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
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

inka requested review of this revision.Thu, Jun 6, 6:59 AM
tomek requested changes to this revision.Thu, Jun 6, 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.Thu, Jun 6, 9:53 AM

Check if response from auth keyserver exists

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