Error: Found invalid key in item viewCount (monographs) {"id":"6926e81438e155664aee70a2","title":null,"selfDestruct":false,"datePublished":0,"password":null,"deleted":true,"viewCount":0,"type":"monograph","synced":false} ❯ Sanitizer.sanitize src/database/sanitizer.ts:56:15 ❯ src/database/sql-collection.ts:205:27 ❯ SQLCollection.put src/database/sql-collection.ts:195:27 ❯ HubConnection.<anonymous> src/api/sync/index.ts:485:47 ❯ HubConnection._invokeClientMethod node_modules/@microsoft/signalr/src/HubConnection.ts:782:31 ❯ HubConnection._processIncomingData node_modules/@microsoft/signalr/src/HubConnection.ts:617:30 ❯ WebSocketTransport.HubConnection.connection.onreceive node_modules/@microsoft/signalr/src/HubConnection.ts:134:57 ❯ WebSocket.webSocket.onmessage node_modules/@microsoft/signalr/src/WebSocketTransport.ts:111:30 ❯ WebSocket.onMessage node_modules/@microsoft/signalr/node_modules/ws/lib/event-target.js:132:16 This error originated in "__e2e__/sync.test.js" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "edge case 1: items updated while push is running". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: Found invalid key in item viewCount (monographs) {"id":"6926e81438e155664aee70a2","title":null,"selfDestruct":false,"datePublished":0,"password":null,"deleted":true,"viewCount":0,"type":"monograph","synced":false} ❯ Sanitizer.sanitize src/database/sanitizer.ts:56:15 ❯ src/database/sql-collection.ts:205:27 ❯ SQLCollection.put src/database/sql-collection.ts:195:27 ❯ HubConnection.<anonymous> src/api/sync/index.ts:485:47 ❯ HubConnection._invokeClientMethod node_modules/@microsoft/signalr/src/HubConnection.ts:782:31 ❯ HubConnection._processIncomingData node_modules/@microsoft/signalr/src/HubConnection.ts:617:30 ❯ WebSocketTransport.HubConnection.connection.onreceive node_modules/@microsoft/signalr/src/HubConnection.ts:134:57 ❯ WebSocket.webSocket.onmessage node_modules/@microsoft/signalr/src/WebSocketTransport.ts:111:30 ❯ WebSocket.onMessage node_modules/@microsoft/signalr/node_modules/ws/lib/event-target.js:132:16 This error originated in "__e2e__/sync.test.js" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "edge case 1: items updated while push is running". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: Found invalid key in item viewCount (monographs) {"id":"6926e81038e155664ae970a2","title":"EDITED TITLE OF MY NOTE!","selfDestruct":false,"datePublished":1764157458895,"password":null,"deleted":false,"viewCount":0,"type":"monograph","synced":false} ❯ Sanitizer.sanitize src/database/sanitizer.ts:56:15 ❯ src/database/sql-collection.ts:205:27 ❯ SQLCollection.put src/database/sql-collection.ts:195:27 ❯ HubConnection.<anonymous> src/api/sync/index.ts:485:47 ❯ HubConnection._invokeClientMethod node_modules/@microsoft/signalr/src/HubConnection.ts:782:31 ❯ HubConnection._processIncomingData node_modules/@microsoft/signalr/src/HubConnection.ts:617:30 ❯ WebSocketTransport.HubConnection.connection.onreceive node_modules/@microsoft/signalr/src/HubConnection.ts:134:57 ❯ WebSocket.webSocket.onmessage node_modules/@microsoft/signalr/src/WebSocketTransport.ts:111:30 ❯ WebSocket.onMessage node_modules/@microsoft/signalr/node_modules/ws/lib/event-target.js:132:16 This error originated in "__e2e__/user-manager.test.js" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "login user after entering incorrect password once". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: Found invalid key in item viewCount (monographs) {"id":"6926e81038e155664ae970a2","title":"EDITED TITLE OF MY NOTE!","selfDestruct":false,"datePublished":1764157458895,"password":null,"deleted":false,"viewCount":0,"type":"monograph","synced":false} ❯ Sanitizer.sanitize src/database/sanitizer.ts:56:15 ❯ src/database/sql-collection.ts:205:27 ❯ SQLCollection.put src/database/sql-collection.ts:195:27 ❯ HubConnection.<anonymous> src/api/sync/index.ts:485:47 ❯ HubConnection._invokeClientMethod node_modules/@microsoft/signalr/src/HubConnection.ts:782:31 ❯ HubConnection._processIncomingData node_modules/@microsoft/signalr/src/HubConnection.ts:617:30 ❯ WebSocketTransport.HubConnection.connection.onreceive node_modules/@microsoft/signalr/src/HubConnection.ts:134:57 ❯ WebSocket.webSocket.onmessage node_modules/@microsoft/signalr/src/WebSocketTransport.ts:111:30 ❯ WebSocket.onMessage node_modules/@microsoft/signalr/node_modules/ws/lib/event-target.js:132:16 This error originated in "__e2e__/user-manager.test.js" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "login user after entering incorrect password once". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: Found invalid key in item viewCount (monographs) {"id":"6926e81038e155664ae970a2","title":"Note 26-11-2025 11:44 AM","selfDestruct":false,"datePublished":1764157458203,"password":null,"deleted":false,"viewCount":0,"type":"monograph","synced":false} ❯ Sanitizer.sanitize src/database/sanitizer.ts:56:15 ❯ src/database/sql-collection.ts:205:27 ❯ SQLCollection.put src/database/sql-collection.ts:195:27 ❯ HubConnection.<anonymous> src/api/sync/index.ts:485:47 ❯ HubConnection._invokeClientMethod node_modules/@microsoft/signalr/src/HubConnection.ts:782:31 ❯ HubConnection._processIncomingData node_modules/@microsoft/signalr/src/HubConnection.ts:617:30 ❯ WebSocketTransport.HubConnection.connection.onreceive node_modules/@microsoft/signalr/src/HubConnection.ts:134:57 ❯ WebSocket.webSocket.onmessage node_modules/@microsoft/signalr/src/WebSocketTransport.ts:111:30 ❯ WebSocket.onMessage node_modules/@microsoft/signalr/node_modules/ws/lib/event-target.js:132:16 This error originated in "__e2e__/user-manager.test.js" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "login user after entering invalid mfa once". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: Found invalid key in item viewCount (monographs) {"id":"6926e81038e155664ae970a2","title":"Note 26-11-2025 11:44 AM","selfDestruct":false,"datePublished":1764157458203,"password":null,"deleted":false,"viewCount":0,"type":"monograph","synced":false} ❯ Sanitizer.sanitize src/database/sanitizer.ts:56:15 ❯ src/database/sql-collection.ts:205:27 ❯ SQLCollection.put src/database/sql-collection.ts:195:27 ❯ HubConnection.<anonymous> src/api/sync/index.ts:485:47 ❯ HubConnection._invokeClientMethod node_modules/@microsoft/signalr/src/HubConnection.ts:782:31 ❯ HubConnection._processIncomingData node_modules/@microsoft/signalr/src/HubConnection.ts:617:30 ❯ WebSocketTransport.HubConnection.connection.onreceive node_modules/@microsoft/signalr/src/HubConnection.ts:134:57 ❯ WebSocket.webSocket.onmessage node_modules/@microsoft/signalr/src/WebSocketTransport.ts:111:30 ❯ WebSocket.onMessage node_modules/@microsoft/signalr/node_modules/ws/lib/event-target.js:132:16 This error originated in "__e2e__/user-manager.test.js" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "login user after entering invalid mfa once". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: Found invalid key in item viewCount (monographs) {"id":"6926e80c38e155664ae470a2","title":"Note 26-11-2025 11:44 AM","selfDestruct":false,"datePublished":1764157455032,"password":null,"deleted":false,"viewCount":0,"type":"monograph","synced":false} ❯ Sanitizer.sanitize src/database/sanitizer.ts:56:15 ❯ src/database/sql-collection.ts:205:27 ❯ SQLCollection.put src/database/sql-collection.ts:195:27 ❯ HubConnection.<anonymous> src/api/sync/index.ts:485:47 ❯ HubConnection._invokeClientMethod node_modules/@microsoft/signalr/src/HubConnection.ts:782:31 ❯ HubConnection._processIncomingData node_modules/@microsoft/signalr/src/HubConnection.ts:617:30 ❯ WebSocketTransport.HubConnection.connection.onreceive node_modules/@microsoft/signalr/src/HubConnection.ts:134:57 ❯ WebSocket.webSocket.onmessage node_modules/@microsoft/signalr/src/WebSocketTransport.ts:111:30 ❯ WebSocket.onMessage node_modules/@microsoft/signalr/node_modules/ws/lib/event-target.js:132:16 This error originated in "__e2e__/user-manager.test.js" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "login user after entering invalid mfa once". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: Found invalid key in item viewCount (monographs) {"id":"6926e80c38e155664ae470a2","title":"Note 26-11-2025 11:44 AM","selfDestruct":false,"datePublished":1764157455032,"password":null,"deleted":false,"viewCount":0,"type":"monograph","synced":false} ❯ Sanitizer.sanitize src/database/sanitizer.ts:56:15 ❯ src/database/sql-collection.ts:205:27 ❯ SQLCollection.put src/database/sql-collection.ts:195:27 ❯ HubConnection.<anonymous> src/api/sync/index.ts:485:47 ❯ HubConnection._invokeClientMethod node_modules/@microsoft/signalr/src/HubConnection.ts:782:31 ❯ HubConnection._processIncomingData node_modules/@microsoft/signalr/src/HubConnection.ts:617:30 ❯ WebSocketTransport.HubConnection.connection.onreceive node_modules/@microsoft/signalr/src/HubConnection.ts:134:57 ❯ WebSocket.webSocket.onmessage node_modules/@microsoft/signalr/src/WebSocketTransport.ts:111:30 ❯ WebSocket.onMessage node_modules/@microsoft/signalr/node_modules/ws/lib/event-target.js:132:16 This error originated in "__e2e__/user-manager.test.js" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "login user after entering invalid mfa once". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: Found invalid key in item viewCount (monographs) {"id":"6926e80c38e155664ae470a2","title":"Note 26-11-2025 11:44 AM","selfDestruct":false,"datePublished":1764157455032,"password":null,"deleted":false,"viewCount":0,"type":"monograph","synced":false} ❯ Sanitizer.sanitize src/database/sanitizer.ts:56:15 ❯ src/database/sql-collection.ts:205:27 ❯ SQLCollection.put src/database/sql-collection.ts:195:27 ❯ HubConnection.<anonymous> src/api/sync/index.ts:485:47 ❯ HubConnection._invokeClientMethod node_modules/@microsoft/signalr/src/HubConnection.ts:782:31 ❯ HubConnection._processIncomingData node_modules/@microsoft/signalr/src/HubConnection.ts:617:30 ❯ WebSocketTransport.HubConnection.connection.onreceive node_modules/@microsoft/signalr/src/HubConnection.ts:134:57 ❯ WebSocket.webSocket.onmessage node_modules/@microsoft/signalr/src/WebSocketTransport.ts:111:30 ❯ WebSocket.onMessage node_modules/@microsoft/signalr/node_modules/ws/lib/event-target.js:132:16 This error originated in "__e2e__/sync.test.js" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "case 3: Device A & B have unsynced changes but server has nothing". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.