AssertionError: expected Map{} to deeply equal Map{} - Expected + Received Map { - "\"electric_test\".\"issues for 181577045_0_3_0.937583a2ce475\"/\"757b6ed3-c528-4427-8c86-217afbe4eba3\"" => Object { - "id": "757b6ed3-c528-4427-8c86-217afbe4eba3", + "\"electric_test\".\"issues for 181577045_0_3_0.937583a2ce475\"/\"635f7ad2-70df-41da-8f4a-fba3b77d48cd\"" => Object { + "id": "635f7ad2-70df-41da-8f4a-fba3b77d48cd", "priority": 10, - "title": "foo1", + "title": "foo2", }, } ❯ test/client.test.ts:173:29 ❯ src/shape.ts:195:7 ❯ Shape.#notify src/shape.ts:194:23 ❯ Shape.#process src/shape.ts:182:12 ❯ src/client.ts:370:17 ❯ ShapeStream.#publish src/client.ts:368:46 ❯ ShapeStream.start src/client.ts:298:22 ❯ processTicksAndRejections node:internal/process/task_queues:95:5 This error originated in "test/client.test.ts" 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 "should resync from scratch on a shape rotation". 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.

Process completed with exit code 1.

first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it