re-enable posthog recordings (#1404) #1499
Annotations
2 errors and 1 warning
|
E2E Tests (Local Emulator, Node 22.x)
Process completed with exit code 1.
|
|
tests/backend/endpoints/api/v1/team-member-profiles.test.ts > can read own profile:
apps/e2e/tests/backend/backend-helpers.ts#L268
Error: Snapshot `can read own profile 6` mismatched
- Expected
+ Received
NiceResponse {
- "status": 200,
+ "status": 401,
"body": {
- "access_token": <stripped field 'access_token'>,
- "refresh_token": <stripped field 'refresh_token'>,
+ "code": "ACCESS_TOKEN_EXPIRED",
+ "details": {
+ "expired_at_millis": 1777882931000,
+ "project_id": "internal",
+ "refresh_token_id": <stripped field 'refresh_token_id'>,
+ "user_id": "<stripped UUID>",
+ },
+ "error": deindent`
+ Access token has expired. Please refresh it and try again. (The access token expired at 2026-05-04T08:22:11.000Z.) Project ID: internal. User ID: <stripped UUID>. Refresh token ID: <stripped UUID>.
+
+ Debug info: Most likely, you fetched the access token before it expired (for example, in a server component, pre-rendered page, or on page load), but then didn't refresh it before it expired. If this is the case, and you're using the SDK, make sure you call getAccessToken() every time you need to use the access token. If you're not using the SDK, make sure you refresh the access token with the refresh endpoint.
+ `,
+ },
+ "headers": Headers {
+ "x-stack-known-error": "ACCESS_TOKEN_EXPIRED",
+ <some fields may have been hidden>,
},
- "headers": Headers { <some fields may have been hidden> },
}
❯ Object.fastSignUp tests/backend/backend-helpers.ts:268:29
❯ signInAndCreateTeam tests/backend/endpoints/api/v1/team-member-profiles.test.ts:10:31
❯ tests/backend/endpoints/api/v1/team-member-profiles.test.ts:152:55
|
|
E2E Tests (Local Emulator, Node 22.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: JarvusInnovations/background-action@v1.0.7, pnpm/action-setup@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/
|