Have change password link point to server #93
daniel-slaughci.yml
on: push
Matrix: Python Client
Docs Build
24s
TypeScript Client
53s
Data Management App
30s
API Service
1m 30s
End-to-End Tests
27m 53s
Trigger Release Workflow
Annotations
16 errors, 8 warnings, and 1 notice
|
Data Management App
Process completed with exit code 1.
|
|
src/api/__tests__/api.spec.ts > api modules > getVisualizationBootstrap > maps bootstrap payloads into client model instances:
apps/data-management/src/api/visualizationBootstrap.ts#L52
Error: [vitest] No "default" export is defined on the "@hydroserver/client" 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("@hydroserver/client"), async (importOriginal) => {
const actual = await importOriginal()
return {
...actual,
// your mocked methods
}
})
❯ Module.getVisualizationBootstrap src/api/visualizationBootstrap.ts:52:29
❯ src/api/__tests__/api.spec.ts:210:28
|
|
src/api/__tests__/api.spec.ts > api modules > listThingSiteSummaries > requests site summaries for the provided workspace id:
apps/data-management/src/api/__tests__/api.spec.ts#L130
AssertionError: promise rejected "Error: [vitest] No "default" export is de… { codeFrame: '…' }" instead of resolving
❯ src/api/__tests__/api.spec.ts:130:58
Caused by: Caused by: Error: [vitest] No "default" export is defined on the "@hydroserver/client" 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("@hydroserver/client"), async (importOriginal) => {
const actual = await importOriginal()
return {
...actual,
// your mocked methods
}
})
❯ Module.listThingSiteSummaries src/api/thingSiteSummaries.ts:10:29
❯ src/api/__tests__/api.spec.ts:130:20
|
|
src/api/__tests__/api.spec.ts > api modules > listThingMarkers > requests thing markers and returns the parsed payload:
apps/data-management/src/api/__tests__/api.spec.ts#L84
AssertionError: promise rejected "Error: [vitest] No "default" export is de… { codeFrame: '…' }" instead of resolving
❯ src/api/__tests__/api.spec.ts:84:38
Caused by: Caused by: Error: [vitest] No "default" export is defined on the "@hydroserver/client" 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("@hydroserver/client"), async (importOriginal) => {
const actual = await importOriginal()
return {
...actual,
// your mocked methods
}
})
❯ Module.listThingMarkers src/api/thingMarkers.ts:8:29
❯ src/api/__tests__/api.spec.ts:84:20
|
|
TypeScript Client
Process completed with exit code 1.
|
|
API Service
Process completed with exit code 1.
|
|
[chromium] › specs/account.spec.ts:71:7 › account management › account deletion removes the user session and invalidates login:
tests/e2e/support/auth.ts#L48
3) [chromium] › specs/account.spec.ts:71:7 › account management › account deletion removes the user session and invalidates login
Error: locator.fill: Test timeout of 60000ms exceeded.
Call log:
- waiting for getByLabel('Email *')
at ../support/auth.ts:48
46 | export async function login(page: Page, email: string, password: string) {
47 | await page.goto('/login')
> 48 | await page.getByLabel('Email *').fill(email)
| ^
49 | await page.getByLabel('Password *').fill(password)
50 | await page.getByRole('button', { name: 'Log in' }).click()
51 | }
at login (/home/runner/work/hydroserver/hydroserver/tests/e2e/support/auth.ts:48:36)
at /home/runner/work/hydroserver/hydroserver/tests/e2e/specs/account.spec.ts:74:5
|
|
[chromium] › specs/account.spec.ts:71:7 › account management › account deletion removes the user session and invalidates login:
tests/e2e/specs/account.spec.ts#L0
3) [chromium] › specs/account.spec.ts:71:7 › account management › account deletion removes the user session and invalidates login
Test timeout of 60000ms exceeded.
|
|
[chromium] › specs/account.spec.ts:23:7 › account management › account menu opens the profile page and profile editing can remove organization details:
tests/e2e/support/auth.ts#L48
2) [chromium] › specs/account.spec.ts:23:7 › account management › account menu opens the profile page and profile editing can remove organization details
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: locator.fill: Test timeout of 60000ms exceeded.
Call log:
- waiting for getByLabel('Email *')
at ../support/auth.ts:48
46 | export async function login(page: Page, email: string, password: string) {
47 | await page.goto('/login')
> 48 | await page.getByLabel('Email *').fill(email)
| ^
49 | await page.getByLabel('Password *').fill(password)
50 | await page.getByRole('button', { name: 'Log in' }).click()
51 | }
at login (/home/runner/work/hydroserver/hydroserver/tests/e2e/support/auth.ts:48:36)
at /home/runner/work/hydroserver/hydroserver/tests/e2e/specs/account.spec.ts:26:5
|
|
[chromium] › specs/account.spec.ts:23:7 › account management › account menu opens the profile page and profile editing can remove organization details:
tests/e2e/specs/account.spec.ts#L0
2) [chromium] › specs/account.spec.ts:23:7 › account management › account menu opens the profile page and profile editing can remove organization details
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Test timeout of 60000ms exceeded.
|
|
[chromium] › specs/account.spec.ts:23:7 › account management › account menu opens the profile page and profile editing can remove organization details:
tests/e2e/support/auth.ts#L48
2) [chromium] › specs/account.spec.ts:23:7 › account management › account menu opens the profile page and profile editing can remove organization details
Error: locator.fill: Test timeout of 60000ms exceeded.
Call log:
- waiting for getByLabel('Email *')
at ../support/auth.ts:48
46 | export async function login(page: Page, email: string, password: string) {
47 | await page.goto('/login')
> 48 | await page.getByLabel('Email *').fill(email)
| ^
49 | await page.getByLabel('Password *').fill(password)
50 | await page.getByRole('button', { name: 'Log in' }).click()
51 | }
at login (/home/runner/work/hydroserver/hydroserver/tests/e2e/support/auth.ts:48:36)
at /home/runner/work/hydroserver/hydroserver/tests/e2e/specs/account.spec.ts:26:5
|
|
[chromium] › specs/account.spec.ts:23:7 › account management › account menu opens the profile page and profile editing can remove organization details:
tests/e2e/specs/account.spec.ts#L0
2) [chromium] › specs/account.spec.ts:23:7 › account management › account menu opens the profile page and profile editing can remove organization details
Test timeout of 60000ms exceeded.
|
|
[chromium] › specs/account.spec.ts:11:7 › account management › user with no workspaces lands on your sites and sees onboarding guidance:
tests/e2e/support/auth.ts#L48
1) [chromium] › specs/account.spec.ts:11:7 › account management › user with no workspaces lands on your sites and sees onboarding guidance
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: locator.fill: Test timeout of 60000ms exceeded.
Call log:
- waiting for getByLabel('Email *')
at ../support/auth.ts:48
46 | export async function login(page: Page, email: string, password: string) {
47 | await page.goto('/login')
> 48 | await page.getByLabel('Email *').fill(email)
| ^
49 | await page.getByLabel('Password *').fill(password)
50 | await page.getByRole('button', { name: 'Log in' }).click()
51 | }
at login (/home/runner/work/hydroserver/hydroserver/tests/e2e/support/auth.ts:48:36)
at /home/runner/work/hydroserver/hydroserver/tests/e2e/specs/account.spec.ts:14:5
|
|
[chromium] › specs/account.spec.ts:11:7 › account management › user with no workspaces lands on your sites and sees onboarding guidance:
tests/e2e/specs/account.spec.ts#L0
1) [chromium] › specs/account.spec.ts:11:7 › account management › user with no workspaces lands on your sites and sees onboarding guidance
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Test timeout of 60000ms exceeded.
|
|
[chromium] › specs/account.spec.ts:11:7 › account management › user with no workspaces lands on your sites and sees onboarding guidance:
tests/e2e/support/auth.ts#L48
1) [chromium] › specs/account.spec.ts:11:7 › account management › user with no workspaces lands on your sites and sees onboarding guidance
Error: locator.fill: Test timeout of 60000ms exceeded.
Call log:
- waiting for getByLabel('Email *')
at ../support/auth.ts:48
46 | export async function login(page: Page, email: string, password: string) {
47 | await page.goto('/login')
> 48 | await page.getByLabel('Email *').fill(email)
| ^
49 | await page.getByLabel('Password *').fill(password)
50 | await page.getByRole('button', { name: 'Log in' }).click()
51 | }
at login (/home/runner/work/hydroserver/hydroserver/tests/e2e/support/auth.ts:48:36)
at /home/runner/work/hydroserver/hydroserver/tests/e2e/specs/account.spec.ts:14:5
|
|
[chromium] › specs/account.spec.ts:11:7 › account management › user with no workspaces lands on your sites and sees onboarding guidance:
tests/e2e/specs/account.spec.ts#L0
1) [chromium] › specs/account.spec.ts:11:7 › account management › user with no workspaces lands on your sites and sees onboarding guidance
Test timeout of 60000ms exceeded.
|
|
Python Client (3.13)
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-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
Python Client (3.11)
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-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
Docs Build
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
Python Client (3.12)
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-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
Data Management App
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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
TypeScript Client
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, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
API Service
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-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
End-to-End Tests
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, actions/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
🎭 Playwright Run Summary
30 failed
[chromium] › specs/account.spec.ts:11:7 › account management › user with no workspaces lands on your sites and sees onboarding guidance
[chromium] › specs/account.spec.ts:23:7 › account management › account menu opens the profile page and profile editing can remove organization details
[chromium] › specs/account.spec.ts:71:7 › account management › account deletion removes the user session and invalidates login
[chromium] › specs/auth.spec.ts:9:7 › authentication › protected pages redirect anonymous users to login
[chromium] › specs/auth.spec.ts:18:7 › authentication › login with seeded owner user reaches the sites page
[chromium] › specs/auth.spec.ts:28:7 › authentication › authenticated users can log out from the account menu
[chromium] › specs/metadata.spec.ts:8:7 › metadata management › metadata page loads workspace and system tabs
[chromium] › specs/metadata.spec.ts:31:7 › metadata management › system metadata entries are visible alongside workspace metadata
[chromium] › specs/metadata.spec.ts:52:7 › metadata management › workspace sensor metadata can be created, updated, and deleted
[chromium] › specs/metadata.spec.ts:95:7 › metadata management › workspace observed property metadata can be created, updated, and deleted
[chromium] › specs/metadata.spec.ts:140:7 › metadata management › workspace processing level metadata can be created, updated, and deleted
[chromium] › specs/metadata.spec.ts:180:7 › metadata management › workspace unit metadata can be created, updated, and deleted
[chromium] › specs/metadata.spec.ts:223:7 › metadata management › workspace result qualifier metadata can be created, updated, and deleted
[chromium] › specs/metadata.spec.ts:273:7 › metadata management › metadata search box filters visible rows
[chromium] › specs/metadata.spec.ts:293:7 › metadata management › metadata in-use items cannot be deleted from the workspace table
[chromium] › specs/orchestration.spec.ts:8:7 › orchestration › orchestration page loads seeded workspace orchestration data
[chromium] › specs/orchestration.spec.ts:25:7 › orchestration › orchestration status filters narrow the task list
[chromium] › specs/orchestration.spec.ts:56:7 › orchestration › orchestration workspace selection updates the visible systems and tasks
[chromium] › specs/sites.spec.ts:18:7 › sites and workspaces › owner can create a workspace from the shared workspace toolbar
[chromium] › specs/sites.spec.ts:52:7 › sites and workspaces › viewer can access a private-workspace site in read-only mode
[chromium] › specs/sites.spec.ts:70:7 › sites and workspaces › sites page search and metadata filters narrow the selected workspace site list
[chromium] › specs/sites.spec.ts:114:7 › sites and workspaces › owner can register a site with metadata and see the saved values on site details
[chromium] › specs/sites.spec.ts:189:7 › sites and workspaces › owner can edit, toggle privacy for, and delete a site with datastream CRUD
[chromium] › specs/sites.spec.ts:327:7 › sites and workspaces › owner privacy toggles affect anonymous site and datastream metadata access
[chromium] › specs/transfers.spec.ts:46:7 › workspace transfers › pending workspace transfers are visible to the destination user
[chromium] › specs/transfers.spec.ts:69:7 › workspace transfers › a pending workspace transfer can be cancelled by the destination user
[chromium] › specs/transfers.spec.ts:105:7 › workspace transfers › a pending workspace transfer can be accepted and ownership moves to the destination user
[chromium] › specs/visualization.spec.ts:164:7 › visualization › visualization filters can narrow datastreams by site
[chromium] › specs/workspaces.spec.ts:7:7 › workspace management › owner can create, validate, update, privatize, and delete a workspace
[chromiu
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
playwright-report
|
48.3 MB |
sha256:34eece991f282519bd803fcd1833289f721d4a1271d5c2856899690eae52a154
|
|