fix: typed error taxonomy, Redis degraded mode, analytics UX states & mobile responsiveness #754
+449
−85
Annotations
10 errors and 1 warning
|
Run client unit tests:
client/hooks/use-bulk-actions.test.ts#L156
AssertionError: expected "vi.fn()" to be called with arguments: [ 1, { status: 'cancelled', …(2) } ]
Number of calls: 0
❯ hooks/use-bulk-actions.test.ts:156:38
|
|
Run client unit tests:
client/hooks/use-bulk-actions.test.ts#L113
AssertionError: expected "vi.fn()" to be called with arguments: [ [ 'Name', 'Category', …(5) ], …(1) ]
Received:
1st vi.fn() call:
@@ -13,10 +13,10 @@
"Spotify",
"Music",
"9.99",
"monthly",
"active",
- "N/A",
+ "30 days",
"N/A",
],
],
]
Number of calls: 1
❯ hooks/use-bulk-actions.test.ts:113:31
|
|
Run client unit tests:
client/hooks/use-bulk-actions.test.ts#L93
AssertionError: expected "vi.fn()" to be called with arguments: [ Any<String>, 'subscriptions-export' ]
Received:
1st vi.fn() call:
[
- Any<String>,
+ undefined,
"subscriptions-export",
]
Number of calls: 1
❯ hooks/use-bulk-actions.test.ts:93:27
|
|
Run client unit tests:
client/app/page.test.ts#L207
AssertionError: expected [ { query: 'email_accounts', …(2) } ] to have a length of +0 but got 1
- Expected
+ Received
- 0
+ 1
❯ app/page.test.ts:207:29
|
|
Run client unit tests:
client/components/onboarding-tour-enhanced.tsx#L183
Error: [vitest] No "EVENTS" export is defined on the "react-joyride-react-19" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:
vi.mock(import("react-joyride-react-19"), async (importOriginal) => {
const actual = await importOriginal()
return {
...actual,
// your mocked methods
}
})
❯ components/onboarding-tour-enhanced.tsx:183:18
❯ onClick components/__tests__/onboarding-tour-enhanced.test.tsx:29:28
❯ executeDispatch node_modules/react-dom/cjs/react-dom-client.development.js:19116:9
❯ runWithFiberInDEV node_modules/react-dom/cjs/react-dom-client.development.js:874:13
❯ processDispatchQueue node_modules/react-dom/cjs/react-dom-client.development.js:19166:19
❯ node_modules/react-dom/cjs/react-dom-client.development.js:19767:9
❯ batchedUpdates$1 node_modules/react-dom/cjs/react-dom-client.development.js:3255:40
❯ dispatchEventForPluginEventSystem node_modules/react-dom/cjs/react-dom-client.development.js:19320:7
This error originated in "components/__tests__/onboarding-tour-enhanced.test.tsx" 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 clear persisted progress on completion". 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.
|
|
Run client unit tests:
client/components/onboarding-tour-enhanced.tsx#L183
Error: [vitest] No "EVENTS" export is defined on the "react-joyride-react-19" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:
vi.mock(import("react-joyride-react-19"), async (importOriginal) => {
const actual = await importOriginal()
return {
...actual,
// your mocked methods
}
})
❯ components/onboarding-tour-enhanced.tsx:183:18
❯ onClick components/__tests__/onboarding-tour-enhanced.test.tsx:17:28
❯ executeDispatch node_modules/react-dom/cjs/react-dom-client.development.js:19116:9
❯ runWithFiberInDEV node_modules/react-dom/cjs/react-dom-client.development.js:874:13
❯ processDispatchQueue node_modules/react-dom/cjs/react-dom-client.development.js:19166:19
❯ node_modules/react-dom/cjs/react-dom-client.development.js:19767:9
❯ batchedUpdates$1 node_modules/react-dom/cjs/react-dom-client.development.js:3255:40
❯ dispatchEventForPluginEventSystem node_modules/react-dom/cjs/react-dom-client.development.js:19320:7
This error originated in "components/__tests__/onboarding-tour-enhanced.test.tsx" 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 persist progress across reloads". 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.
|
|
Run client unit tests:
client/components/onboarding-tour-enhanced.tsx#L183
Error: [vitest] No "EVENTS" export is defined on the "react-joyride-react-19" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:
vi.mock(import("react-joyride-react-19"), async (importOriginal) => {
const actual = await importOriginal()
return {
...actual,
// your mocked methods
}
})
❯ components/onboarding-tour-enhanced.tsx:183:18
❯ onClick components/__tests__/onboarding-tour-enhanced.test.tsx:23:28
❯ executeDispatch node_modules/react-dom/cjs/react-dom-client.development.js:19116:9
❯ runWithFiberInDEV node_modules/react-dom/cjs/react-dom-client.development.js:874:13
❯ processDispatchQueue node_modules/react-dom/cjs/react-dom-client.development.js:19166:19
❯ node_modules/react-dom/cjs/react-dom-client.development.js:19767:9
❯ batchedUpdates$1 node_modules/react-dom/cjs/react-dom-client.development.js:3255:40
❯ dispatchEventForPluginEventSystem node_modules/react-dom/cjs/react-dom-client.development.js:19320:7
This error originated in "components/__tests__/onboarding-tour-enhanced.test.tsx" 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 handle tour skip". 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.
|
|
Run client unit tests:
client/components/onboarding-tour-enhanced.tsx#L183
Error: [vitest] No "EVENTS" export is defined on the "react-joyride-react-19" mock. Did you forget to return it from "vi.mock"?
If you need to partially mock a module, you can use "importOriginal" helper inside:
vi.mock(import("react-joyride-react-19"), async (importOriginal) => {
const actual = await importOriginal()
return {
...actual,
// your mocked methods
}
})
❯ components/onboarding-tour-enhanced.tsx:183:18
❯ onClick components/__tests__/onboarding-tour-enhanced.test.tsx:29:28
❯ executeDispatch node_modules/react-dom/cjs/react-dom-client.development.js:19116:9
❯ runWithFiberInDEV node_modules/react-dom/cjs/react-dom-client.development.js:874:13
❯ processDispatchQueue node_modules/react-dom/cjs/react-dom-client.development.js:19166:19
❯ node_modules/react-dom/cjs/react-dom-client.development.js:19767:9
❯ batchedUpdates$1 node_modules/react-dom/cjs/react-dom-client.development.js:3255:40
❯ dispatchEventForPluginEventSystem node_modules/react-dom/cjs/react-dom-client.development.js:19320:7
This error originated in "components/__tests__/onboarding-tour-enhanced.test.tsx" 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 handle tour completion". 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.
|
|
Run client unit tests:
client/hooks/use-bulk-actions.test.ts#L181
TypeError: Cannot destructure property 'onConfirm' of 'object null' as it is null.
❯ hooks/use-bulk-actions.test.ts:181:52
❯ onConfirm hooks/use-bulk-actions.ts:200:9
❯ hooks/use-bulk-actions.test.ts:182:9
❯ Object.handleBulkCancel hooks/use-bulk-actions.ts:193:5
❯ hooks/use-bulk-actions.test.ts:186:24
❯ node_modules/@testing-library/react/dist/act-compat.js:47:24
❯ process.env.NODE_ENV.exports.act node_modules/react/cjs/react.development.js:814:22
❯ Proxy.<anonymous> node_modules/@testing-library/react/dist/act-compat.js:46:25
This error originated in "hooks/use-bulk-actions.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 "handles subscriptions with null renewsIn in cancellation". 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.
|
|
Run client unit tests:
client/hooks/use-bulk-actions.test.ts#L148
TypeError: Cannot destructure property 'onConfirm' of 'object null' as it is null.
❯ hooks/use-bulk-actions.test.ts:148:52
❯ onConfirm hooks/use-bulk-actions.ts:200:9
❯ hooks/use-bulk-actions.test.ts:149:9
❯ Object.handleBulkCancel hooks/use-bulk-actions.ts:193:5
❯ hooks/use-bulk-actions.test.ts:153:24
❯ node_modules/@testing-library/react/dist/act-compat.js:47:24
❯ process.env.NODE_ENV.exports.act node_modules/react/cjs/react.development.js:814:22
❯ Proxy.<anonymous> node_modules/@testing-library/react/dist/act-compat.js:46:25
This error originated in "hooks/use-bulk-actions.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 "cancels subscriptions and calculates activeUntil correctly". 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.
|
|
Run actions/upload-artifact@v7
No files were found with the provided path: client/coverage/. No artifacts will be uploaded.
|
background
wait
wait-all
cancel
Loading