fix: add CellErrorBoundary to prevent Firefox DOMException from crashing table page #10901
charliedowlerpr.yml
on: pull_request
Select Tests to Run
34s
Enforce Exact Dependency Versions
6s
Build & Test
1m 35s
Post Test Selection Comment
31s
Cleanup test schemas
Annotations
15 warnings
|
Build & Test:
packages/backend/src/ee/services/AiAgentService/AiAgentService.ts#L1417
Direct ability.can/cannot calls bypass audit logging. Use `const ability = this.createAuditedAbility(user);` then `ability.cannot(...)` instead
|
|
Build & Test:
packages/backend/src/ee/services/AiAgentService/AiAgentService.ts#L1341
Direct ability.can/cannot calls bypass audit logging. Use `const ability = this.createAuditedAbility(user);` then `ability.can(...)` instead
|
|
Build & Test:
packages/backend/src/ee/services/AiAgentService/AiAgentService.ts#L1298
Direct ability.can/cannot calls bypass audit logging. Use `const ability = this.createAuditedAbility(user);` then `ability.can(...)` instead
|
|
Build & Test:
packages/backend/src/ee/services/AiAgentService/AiAgentService.ts#L1161
Direct ability.can/cannot calls bypass audit logging. Use `const ability = this.createAuditedAbility(user);` then `ability.cannot(...)` instead
|
|
Build & Test:
packages/backend/src/ee/services/AiAgentService/AiAgentService.ts#L1098
Direct ability.can/cannot calls bypass audit logging. Use `const ability = this.createAuditedAbility(user);` then `ability.cannot(...)` instead
|
|
Build & Test:
packages/backend/src/ee/services/AiAgentService/AiAgentService.ts#L1039
Direct ability.can/cannot calls bypass audit logging. Use `const ability = this.createAuditedAbility(user);` then `ability.cannot(...)` instead
|
|
Build & Test:
packages/backend/src/ee/services/AiAgentService/AiAgentService.ts#L736
Direct ability.can/cannot calls bypass audit logging. Use `const ability = this.createAuditedAbility(user);` then `ability.can(...)` instead
|
|
Build & Test:
packages/backend/src/ee/services/AiAgentService/AiAgentService.ts#L400
Direct ability.can/cannot calls bypass audit logging. Use `const ability = this.createAuditedAbility(user);` then `ability.can(...)` instead
|
|
Build & Test:
packages/backend/src/ee/services/AiAgentService/AiAgentService.ts#L336
Direct ability.can/cannot calls bypass audit logging. Use `const ability = this.createAuditedAbility(user);` then `ability.can(...)` instead
|
|
Build & Test:
packages/backend/src/ee/services/AiAgentAdminService.ts#L33
Direct ability.can/cannot calls bypass audit logging. Use `const ability = this.createAuditedAbility(user);` then `ability.cannot(...)` instead
|
|
E2E: App (4/5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jsdaniell/create-json@b8e77fa01397ca39cc4a6198cc29a3be5481afef. 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/
|
|
E2E: App (3/5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jsdaniell/create-json@b8e77fa01397ca39cc4a6198cc29a3be5481afef. 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/
|
|
E2E: App (2/5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jsdaniell/create-json@b8e77fa01397ca39cc4a6198cc29a3be5481afef. 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/
|
|
E2E: App (5/5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jsdaniell/create-json@b8e77fa01397ca39cc4a6198cc29a3be5481afef. 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/
|
|
E2E: App (1/5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jsdaniell/create-json@b8e77fa01397ca39cc4a6198cc29a3be5481afef. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
lightdash~lightdash~IDQ621.dockerbuild
|
36.3 KB |
sha256:4716f23d7c3c7f6afcf3c4ac36e0e1bf47760af8753df5e91d798650b72a5d8a
|
|