Skip to content

in-memory realtime sync #3684

in-memory realtime sync

in-memory realtime sync #3684

Triggered via pull request September 24, 2024 00:02
@kyscott18kyscott18
synchronize #1115
kjs/mem
Status Cancelled
Total duration 1m 3s
Artifacts

main.yml

on: pull_request
Matrix: Test [common]
Matrix: Test [core]
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 3 warnings
Lint
Canceling since a higher priority waiting request for 'Main-kjs/mem' exists
Lint
Property 'pruneByBlock' does not exist on type 'SyncStore'.
Lint
The operation was canceled.
Test [core] (Postgres)
Canceling since a higher priority waiting request for 'Main-kjs/mem' exists
Test [core] (Postgres)
The operation was canceled.
Test [core] (SQLite)
Canceling since a higher priority waiting request for 'Main-kjs/mem' exists
Test [core] (SQLite)
The operation was canceled.
Test [common] (Node)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test [create-ponder]
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/