fix(sqlite-native): restore kv error hook #2129
NathanFlurryfrontend.yml
on: pull_request
Dashboard / Quality Check
13s
RivetKit / Quality Check
15s
Dashboard / Type Check
1m 5s
RivetKit / Type Check
56s
Matrix: dashboard-e2e-cloud
Annotations
25 errors and 7 warnings
|
Dashboard / E2E Tests / Cloud (1/1)
Process completed with exit code 1.
|
|
Dashboard / E2E Tests / Cloud (1/1)
@rivetkit/rivetkit-native#build: command (/home/runner/work/rivet/rivet/rivetkit-typescript/packages/rivetkit-native) /home/runner/setup-pnpm/node_modules/.bin/pnpm run build exited (1)
|
|
format:
rivetkit-typescript/packages/rivetkit/fixtures/driver-test-suite/registry-static.ts#L1
Formatter would have printed the following content:
|
|
format:
rivetkit-typescript/packages/rivetkit/fixtures/driver-test-suite/registry-dynamic.ts#L1
Formatter would have printed the following content:
|
|
format:
rivetkit-typescript/packages/rivetkit/fixtures/driver-test-suite/lifecycle-hooks.ts#L1
Formatter would have printed the following content:
|
|
format:
rivetkit-typescript/packages/rivetkit/fixtures/driver-test-suite/db-pragma-migration.ts#L1
Formatter would have printed the following content:
|
|
format:
rivetkit-typescript/packages/rivetkit-native/wrapper.d.ts#L1
Formatter would have printed the following content:
|
|
format:
rivetkit-typescript/packages/rivetkit-native/index.d.ts#L1
Formatter would have printed the following content:
|
|
format:
rivetkit-typescript/packages/engine-runner/src/websocket-tunnel-adapter.ts#L1
Formatter would have printed the following content:
|
|
format:
rivetkit-typescript/packages/engine-runner/src/tunnel.ts#L1
Formatter would have printed the following content:
|
|
format:
rivetkit-typescript/packages/engine-runner/src/mod.ts#L1
Formatter would have printed the following content:
|
|
format:
rivetkit-typescript/packages/engine-runner-protocol/src/index.ts#L1
Formatter would have printed the following content:
|
|
Dashboard / Quality Check
Process completed with exit code 1.
|
|
format:
frontend/vite.engine.config.ts#L1
Formatter would have printed the following content:
|
|
format:
frontend/src/components/use-deployment-logs-stream.ts#L1
Formatter would have printed the following content:
|
|
format:
frontend/src/components/onboarding/footer.tsx#L1
Formatter would have printed the following content:
|
|
format:
frontend/src/components/actors/workflow/workflow-visualizer.tsx#L1
Formatter would have printed the following content:
|
|
format:
frontend/src/components/actors/workflow/workflow-to-xyflow.ts#L1
Formatter would have printed the following content:
|
|
format:
frontend/src/components/actors/database/database-table.tsx#L1
Formatter would have printed the following content:
|
|
format:
frontend/src/components/actors/actor-status-label.tsx#L1
Formatter would have printed the following content:
|
|
format:
frontend/src/components/actors/actor-database.tsx#L1
Formatter would have printed the following content:
|
|
RivetKit / Type Check
Process completed with exit code 1.
|
|
RivetKit / Type Check
@rivetkit/sqlite-native#build: command (/home/runner/work/rivet/rivet/rivetkit-typescript/packages/sqlite-native) /home/runner/setup-pnpm/node_modules/.bin/pnpm run build exited (1)
|
|
Dashboard / Type Check
Process completed with exit code 1.
|
|
Dashboard / Type Check
@rivetkit/rivetkit-native#build: command (/home/runner/work/rivet/rivet/rivetkit-typescript/packages/rivetkit-native) /home/runner/setup-pnpm/node_modules/.bin/pnpm run build exited (1)
|
|
Dashboard / E2E Tests / Cloud (1/1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, 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/
|
|
Dashboard / E2E Tests / Cloud (1/1)
No files were found with the provided path: frontend/test-results/. No artifacts will be uploaded.
|
|
Dashboard / E2E Tests / Cloud (1/1)
No files were found with the provided path: frontend/playwright-report/. No artifacts will be uploaded.
|
|
RivetKit / Quality Check
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 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/
|
|
Dashboard / Quality Check
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 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/
|
|
RivetKit / Type Check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, 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/
|
|
Dashboard / Type Check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, 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/
|