Instead of dispatching a call from Socket, we should use the unified mechanism owned by KeyserverConnectionHandler. This way, we can avoid multiple simultaneous recoveries being dispatched at once.
Depends on D11215
Paths
| Differential D11216 Authored by ashoat on Mar 3 2024, 8:49 PM.
Tags None Referenced Files
Subscribers None
Details Summary Instead of dispatching a call from Socket, we should use the unified mechanism owned by KeyserverConnectionHandler. This way, we can avoid multiple simultaneous recoveries being dispatched at once. Depends on D11215 Test Plan Part 4.4 of this test plan: https://gist.github.com/Ashoat/75ab690d5c53cdd68a51b02e03e27c58
Diff Detail
Event Timelineashoat added a child revision: D11217: [lib][native] Try session recovery on web too for policy acknowledgment crash loop. Harbormaster completed remote builds in B27272: Diff 37749.Mar 3 2024, 9:21 PM2024-03-03 21:21:08 (UTC-8) This revision is now accepted and ready to land.Mar 4 2024, 2:48 AM2024-03-04 02:48:59 (UTC-8) Closed by commit rCOMMb90d5f3e5aa8: [lib][native] Use unified keyserver session recovery in native/socket.react.js (authored by ashoat). · Explain WhyMar 5 2024, 8:52 AM2024-03-05 08:52:13 (UTC-8) This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 37841 lib/socket/socket.react.js
lib/types/socket-types.js
native/socket.react.js
|