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
Unknown Object (File)
Fri, Nov 15, 7:53 AM
Unknown Object (File)
Thu, Nov 14, 10:51 AM
Unknown Object (File)
Mon, Nov 11, 4:23 AM
Unknown Object (File)
Mon, Nov 11, 3:56 AM
Unknown Object (File)
Sun, Nov 10, 10:01 PM
Unknown Object (File)
Sun, Nov 10, 7:30 PM
Unknown Object (File)
Sun, Nov 10, 5:47 PM
Unknown Object (File)
Sun, Nov 10, 12:34 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.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