Page MenuHomePhabricator

[keyserver] Log on keyserver when INITIAL_NOTIFICATIONS_ENCRYPTED_MESSAGE is sent to the client
ClosedPublic

Authored by angelika on Mon, Nov 18, 5:29 AM.
Tags
None
Referenced Files
F3351589: D13951.id45858.diff
Sat, Nov 23, 2:40 AM
F3349814: D13951.diff
Fri, Nov 22, 7:18 PM
Unknown Object (File)
Thu, Nov 21, 7:09 AM
Unknown Object (File)
Thu, Nov 21, 3:43 AM
Unknown Object (File)
Tue, Nov 19, 10:00 PM
Unknown Object (File)
Tue, Nov 19, 7:12 PM
Unknown Object (File)
Tue, Nov 19, 6:57 AM
Unknown Object (File)
Tue, Nov 19, 5:45 AM
Subscribers

Details

Summary
Test Plan

Flow and put the log somewhere else and check if it logs (I don't know how to trigger olmNotificationsSessionMissing)

Diff Detail

Repository
rCOMM Comm
Branch
graszka22/ENG-9932
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

Just wondering, what do you think of this style?

const { userID, cookieID, sessionID } = viewer;
const data = { userID, cookieID, sessionID };
console.log(
  'Sending INITIAL_NOTIFICATIONS_ENCRYPTED_MESSAGE ' +
    JSON.stringify(data),
);

Could work both here and in D13952.

Just wondering, what do you think of this style?

const { userID, cookieID, sessionID } = viewer;
const data = { userID, cookieID, sessionID };
console.log(
  'Sending INITIAL_NOTIFICATIONS_ENCRYPTED_MESSAGE ' +
    JSON.stringify(data),
);

Could work both here and in D13952.

I prefer this style too

keyserver/src/socket/socket.js
476

Overall, this seems strange to log identifiable data, but probably it's fine for @ashoat's private keyserver

This revision is now accepted and ready to land.Tue, Nov 19, 1:49 AM