cli oauth #144
alxnddrAnnotations
16 errors and 10 warnings
|
e2e (oss-60)
Process completed with exit code 1.
|
|
tests/e2e/oauth.e2e.test.ts > oauth e2e > persists the OAuth profile and `auth list` verifies it through the CLI:
tests/e2e/oauth.e2e.test.ts#L185
AssertionError: expected 'auth-failed' to be 'ok' // Object.is equality
Expected: "ok"
Received: "auth-failed"
❯ tests/e2e/oauth.e2e.test.ts:185:38
|
|
tests/e2e/oauth.e2e.test.ts > oauth e2e > refreshes the access token against the real token endpoint and the new token works:
tests/e2e/oauth.e2e.test.ts#L136
AssertionError: expected 401 to be 200 // Object.is equality
- Expected
+ Received
- 200
+ 401
❯ tests/e2e/oauth.e2e.test.ts:136:24
|
|
tests/e2e/oauth.e2e.test.ts > oauth e2e > registers a client, completes consent, and the bearer token authenticates the REST API:
tests/e2e/oauth.e2e.test.ts#L122
AssertionError: Unauthenticated: expected 401 to be 200 // Object.is equality
- Expected
+ Received
- 200
+ 401
❯ tests/e2e/oauth.e2e.test.ts:122:50
|
|
e2e (oss-61)
Process completed with exit code 1.
|
|
tests/e2e/oauth.e2e.test.ts > oauth e2e > persists the OAuth profile and `auth list` verifies it through the CLI:
tests/e2e/oauth.e2e.test.ts#L185
AssertionError: expected 'auth-failed' to be 'ok' // Object.is equality
Expected: "ok"
Received: "auth-failed"
❯ tests/e2e/oauth.e2e.test.ts:185:38
|
|
tests/e2e/oauth.e2e.test.ts > oauth e2e > refreshes the access token against the real token endpoint and the new token works:
tests/e2e/oauth.e2e.test.ts#L136
AssertionError: expected 401 to be 200 // Object.is equality
- Expected
+ Received
- 200
+ 401
❯ tests/e2e/oauth.e2e.test.ts:136:24
|
|
tests/e2e/oauth.e2e.test.ts > oauth e2e > registers a client, completes consent, and the bearer token authenticates the REST API:
tests/e2e/oauth.e2e.test.ts#L122
AssertionError: Unauthenticated: expected 401 to be 200 // Object.is equality
- Expected
+ Received
- 200
+ 401
❯ tests/e2e/oauth.e2e.test.ts:122:50
|
|
e2e (ee-60)
Process completed with exit code 1.
|
|
tests/e2e/oauth.e2e.test.ts > oauth e2e > persists the OAuth profile and `auth list` verifies it through the CLI:
tests/e2e/oauth.e2e.test.ts#L185
AssertionError: expected 'auth-failed' to be 'ok' // Object.is equality
Expected: "ok"
Received: "auth-failed"
❯ tests/e2e/oauth.e2e.test.ts:185:38
|
|
tests/e2e/oauth.e2e.test.ts > oauth e2e > refreshes the access token against the real token endpoint and the new token works:
tests/e2e/oauth.e2e.test.ts#L136
AssertionError: expected 401 to be 200 // Object.is equality
- Expected
+ Received
- 200
+ 401
❯ tests/e2e/oauth.e2e.test.ts:136:24
|
|
tests/e2e/oauth.e2e.test.ts > oauth e2e > registers a client, completes consent, and the bearer token authenticates the REST API:
tests/e2e/oauth.e2e.test.ts#L122
AssertionError: Unauthenticated: expected 401 to be 200 // Object.is equality
- Expected
+ Received
- 200
+ 401
❯ tests/e2e/oauth.e2e.test.ts:122:50
|
|
e2e (ee-61)
Process completed with exit code 1.
|
|
tests/e2e/oauth.e2e.test.ts > oauth e2e > persists the OAuth profile and `auth list` verifies it through the CLI:
tests/e2e/oauth.e2e.test.ts#L185
AssertionError: expected 'auth-failed' to be 'ok' // Object.is equality
Expected: "ok"
Received: "auth-failed"
❯ tests/e2e/oauth.e2e.test.ts:185:38
|
|
tests/e2e/oauth.e2e.test.ts > oauth e2e > refreshes the access token against the real token endpoint and the new token works:
tests/e2e/oauth.e2e.test.ts#L136
AssertionError: expected 401 to be 200 // Object.is equality
- Expected
+ Received
- 200
+ 401
❯ tests/e2e/oauth.e2e.test.ts:136:24
|
|
tests/e2e/oauth.e2e.test.ts > oauth e2e > registers a client, completes consent, and the bearer token authenticates the REST API:
tests/e2e/oauth.e2e.test.ts#L122
AssertionError: Unauthenticated: expected 401 to be 200 // Object.is equality
- Expected
+ Received
- 200
+ 401
❯ tests/e2e/oauth.e2e.test.ts:122:50
|
|
e2e (oss-58)
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 16th, 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/
|
|
e2e (ee-58)
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 16th, 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/
|
|
e2e (oss-60)
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
e2e (oss-59)
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 16th, 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/
|
|
e2e (ee-59)
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 16th, 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/
|
|
e2e (ee-head)
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 16th, 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/
|
|
e2e (oss-61)
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
e2e (ee-60)
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
e2e (oss-head)
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 16th, 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/
|
|
e2e (ee-61)
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
metabase-logs-ee-60
|
351 KB |
sha256:eb074d0557e7a99c2e194700541e0a2c3a5e90772ec49e1a6eb226835a2ba1c4
|
|
|
metabase-logs-ee-61
|
485 KB |
sha256:8f5ebe375fa750fab4361b24641a535a9c4eeeac1f5963b3a4f11ce8b97d32e7
|
|
|
metabase-logs-oss-60
|
313 KB |
sha256:eba87d5b1fb9819cfe9f55d63166542a9a5f4ff5f6f51cf624a8faa8565e799b
|
|
|
metabase-logs-oss-61
|
434 KB |
sha256:f0df90b2c812184d2acfb7a2c470c67bc812f278203cec5e960142d8b0bb1ab5
|
|