Page MenuHomePhabricator

[keyserver] Track closed state in TunnelbrokerSocket
ClosedPublic

Authored by ashoat on Mar 26 2024, 8:24 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Apr 14, 7:28 PM
Unknown Object (File)
Sun, Apr 14, 7:28 PM
Unknown Object (File)
Sun, Apr 14, 7:27 PM
Unknown Object (File)
Sun, Apr 14, 7:26 PM
Unknown Object (File)
Tue, Apr 9, 7:55 AM
Unknown Object (File)
Sat, Apr 6, 4:19 AM
Unknown Object (File)
Fri, Apr 5, 12:14 PM
Unknown Object (File)
Fri, Apr 5, 9:23 AM
Subscribers

Details

Summary

This diff makes sure we don't respond to 'open' and 'close' events that come after a 'close' event. It mirrors code in lib/socket/socket.react.js.

We need this additional state so that in the on('open' block, we can differentiate the state prior to initialization to the state after closure.

Test Plan

I'm actually not sure how to reproduce an open or close event after a close event. Just adding this code because it was in the other class, and I don't think it will hurt

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable