Details
Details
Mocked connection inintialization message to have invalid token. Upon receiving response, the metadata table was cleared. Closing connection caused a retry, on which login was performed and new metadata was created.
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
keyserver/src/socket/tunnelbroker.js | ||
---|---|---|
119 | Confused a bit why this was moved out of createNewTunnelbrokerSocket. We end up calling fetchIdentityInfo even if !encryptionKey. Is this intentional? If we move this call back into createNewTunnelbrokerSocket, then we could skip it in that case. |
keyserver/src/socket/tunnelbroker.js | ||
---|---|---|
119 | Intentional. Both ways would work, I just assumed my way was cleaner. But your suggestion makes sense as well, so I'll move it back. |