fix: bug returning undefined from area.byCode #268
joaquimdsAnnotations
6 errors and 1 warning
|
test
Process completed with exit code 1.
|
|
tests/unit/server/adaptors/mailchimp.test.ts > Mailchimp adaptor tests > fetched records use merge field names, not tags, as JSON keys:
tests/unit/server/adaptors/mailchimp.test.ts#L583
Error: Test timed out in 30000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/unit/server/adaptors/mailchimp.test.ts:583:3
|
|
tests/unit/server/adaptors/mailchimp.test.ts > Mailchimp adaptor tests > existing merge fields are not wiped when updateRecords is called:
tests/unit/server/adaptors/mailchimp.test.ts#L511
Error: Test timed out in 30000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/unit/server/adaptors/mailchimp.test.ts:511:3
|
|
tests/unit/server/adaptors/mailchimp.test.ts > Mailchimp adaptor tests > tagRecords updates a record:
tests/unit/server/adaptors/mailchimp.test.ts#L353
Error: Test timed out in 30000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/unit/server/adaptors/mailchimp.test.ts:353:3
|
|
tests/unit/server/adaptors/mailchimp.test.ts > Mailchimp adaptor tests > updateRecords creates merge field and deleteColumn removes it:
tests/unit/server/adaptors/mailchimp.test.ts#L215
Error: Test timed out in 30000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ tests/unit/server/adaptors/mailchimp.test.ts:215:3
|
|
tests/feature/enrichDataSource.test.ts:
tests/feature/enrichDataSource.test.ts#L29
TypeError: Cannot read properties of undefined (reading 'googlesheets')
❯ tests/feature/enrichDataSource.test.ts:29:48
|
|
test
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. 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/
|