You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we experience a strange issue with tolgee while testing.
We have few tests in our codebase, but sometimes we have strange error and only in Bitbucket pipelines:
Vitest caught 1 unhandled error during the test run.
This might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.
⎯⎯⎯⎯⎯ Uncaught Exception ⎯⎯⎯⎯⎯
ReferenceError: window is not defined
❯ Object.unsubscribe node_modules/@tolgee/web/src/package/tools/extension.ts:18:14
❯ removeEventListener node_modules/@tolgee/web/src/package/tools/extension.ts:43:18
❯ Timeout.expire [as _onTimeout] node_modules/@tolgee/web/src/package/tools/extension.ts:46:29
❯ listOnTimeout node:internal/timers:569:17
❯ processTimers node:internal/timers:512:7
This error originated in "src/features/component/components/__tests__/Component.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
This error was caught after test environment was torn down. Make sure to cancel any running tasks before test finishes:
- cancel timeouts using clearTimeout and clearInterval
- wait for promises to resolve using the await keyword
When we run tests locally, everything works great, but when the tests start in the Bitbucket pipeline, it sometimes work, sometimes throw error. Don't know why, and why it throws errors. If we run tests without the tolgee inside the components, it works every time. We are using next.js 14 with app directory, and server components
Hi, we experience a strange issue with tolgee while testing.
We have few tests in our codebase, but sometimes we have strange error and only in Bitbucket pipelines:
When we run tests locally, everything works great, but when the tests start in the Bitbucket pipeline, it sometimes work, sometimes throw error. Don't know why, and why it throws errors. If we run tests without the tolgee inside the components, it works every time. We are using next.js 14 with app directory, and server components
Our environment:
The text was updated successfully, but these errors were encountered: