fix: emergency override timezone+overlap, broadcast fire-and-forget, … #34
Ash007devci-cd-pipeline.yml
on: push
Server — Build & Test
1m 22s
Client — Build & Lint
48s
Security Audit
32s
Deploy
4s
Annotations
8 errors and 4 warnings
|
src/__tests__/epic6/adminBroadcast.test.ts > Epic 6 US 2: Admin Broadcast Email > should use fallback name "User" when first_name and last_name are empty:
server/src/__tests__/epic6/adminBroadcast.test.ts#L253
AssertionError: expected "vi.fn()" to be called with arguments: [ 'noname@campus.edu', 'User', …(1) ]
Number of calls: 0
❯ src/__tests__/epic6/adminBroadcast.test.ts:253:40
|
|
src/__tests__/epic6/adminBroadcast.test.ts > Epic 6 US 2: Admin Broadcast Email > should write an audit log entry after sending:
server/src/__tests__/epic6/adminBroadcast.test.ts#L239
AssertionError: expected "vi.fn()" to be called with arguments: [ 'audit_logs' ]
Received:
1st vi.fn() call:
[
- "audit_logs",
+ "users",
]
Number of calls: 1
❯ src/__tests__/epic6/adminBroadcast.test.ts:239:26
|
|
src/__tests__/epic6/adminBroadcast.test.ts > Epic 6 US 2: Admin Broadcast Email > should handle email send exceptions gracefully:
server/src/__tests__/epic6/adminBroadcast.test.ts#L226
AssertionError: expected undefined to be 2 // Object.is equality
- Expected:
2
+ Received:
undefined
❯ src/__tests__/epic6/adminBroadcast.test.ts:226:45
|
|
src/__tests__/epic6/adminBroadcast.test.ts > Epic 6 US 2: Admin Broadcast Email > should handle partial email failures gracefully:
server/src/__tests__/epic6/adminBroadcast.test.ts#L207
AssertionError: expected undefined to be 2 // Object.is equality
- Expected:
2
+ Received:
undefined
❯ src/__tests__/epic6/adminBroadcast.test.ts:207:45
|
|
src/__tests__/epic6/adminBroadcast.test.ts > Epic 6 US 2: Admin Broadcast Email > should deduplicate users by email (same email appears multiple times):
server/src/__tests__/epic6/adminBroadcast.test.ts#L188
AssertionError: expected "vi.fn()" to be called 2 times, but got 0 times
❯ src/__tests__/epic6/adminBroadcast.test.ts:188:40
|
|
src/__tests__/epic6/adminBroadcast.test.ts > Epic 6 US 2: Admin Broadcast Email > should send broadcast email to all users:
server/src/__tests__/epic6/adminBroadcast.test.ts#L121
AssertionError: expected undefined to be 3 // Object.is equality
- Expected:
3
+ Received:
undefined
❯ src/__tests__/epic6/adminBroadcast.test.ts:121:45
|
|
src/__tests__/epic4/approvalWorkflow.test.ts:
server/src/services/bookingService.ts#L10
Error: [vitest] There was an error when mocking a module. If you are using "vi.mock" factory, make sure there are no top level variables inside, since this call is hoisted to top of the file. Read more: https://vitest.dev/api/vi.html#vi-mock
❯ src/services/bookingService.ts:10:1
Caused by: Caused by: ReferenceError: Cannot access 'mockSupabase' before initialization
❯ src/__tests__/epic4/approvalWorkflow.test.ts:24:15
|
|
src/__tests__/epic3/us3.7-waitlist.test.ts > US 3.7: Waitlist Notification > Waitlist Notification on Booking Cancellation > should notify the first user in the waitlist when a booking is cancelled:
server/src/__tests__/epic3/us3.7-waitlist.test.ts#L255
AssertionError: expected 403 to be 201 // Object.is equality
- Expected
+ Received
- 201
+ 403
❯ src/__tests__/epic3/us3.7-waitlist.test.ts:255:39
|
|
Security Audit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Client — Build & Lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Server — Build & Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Deploy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|