Introduce logging for unexpected incoming urgent values
This commit is contained in:
parent
f92be05b15
commit
5fcf97b43b
8 changed files with 278 additions and 83 deletions
|
@ -19,6 +19,7 @@ const { insertSentProto, updateConversation } = dataInterface;
|
|||
export const sendTypesEnum = z.enum([
|
||||
// Core user interactions, default urgent
|
||||
'message',
|
||||
'story', // non-urgent
|
||||
'callingMessage', // excluded from send log; only call-initiation messages are urgent
|
||||
'deleteForEveryone',
|
||||
'expirationTimerUpdate', // non-urgent
|
||||
|
@ -46,6 +47,14 @@ export const sendTypesEnum = z.enum([
|
|||
'keySyncRequest', // urgent because it blocks the link process
|
||||
'pniIdentitySyncRequest', // urgent because we need our PNI to be fully functional
|
||||
|
||||
// The actual sync messages, which we never send, just receive - non-urgent
|
||||
'blockSync',
|
||||
'configurationSync',
|
||||
'contactSync',
|
||||
'groupSync',
|
||||
'keySync',
|
||||
'pniIdentitySync',
|
||||
|
||||
// Syncs, default non-urgent
|
||||
'fetchLatestManifestSync',
|
||||
'fetchLocalProfileSync',
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue