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)
Tue, Apr 22, 5:09 AM
Unknown Object (File)
Wed, Apr 16, 3:53 PM
Unknown Object (File)
Wed, Apr 16, 7:27 AM
Unknown Object (File)
Wed, Apr 16, 6:30 AM
Unknown Object (File)
Tue, Apr 15, 11:48 PM
Unknown Object (File)
Tue, Apr 15, 5:59 AM
Unknown Object (File)
Wed, Apr 9, 11:40 AM
Unknown Object (File)
Feb 28 2025, 5:30 AM
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
Branch
inka/userStore
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

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