Error: Error: missing field `pageSize` ❯ module.exports.__wbindgen_throw dist/cjs/js_api.js:811:11 ❯ wasm_bindgen::throw_str::h111e4f9d3cd59f2a wasm:/wasm/rain_orderbook_js_api.wasm-003e1d3e:1:622185 ❯ wasm_bindgen_futures::future_to_promise::{{closure}}::{{closure}}::hd2e80d741f8f07ac wasm:/wasm/rain_orderbook_js_api.wasm-003e1d3e:1:186967 ❯ wasm_bindgen_futures::queue::QueueState::run_all::h5ef90423af5e5f2a wasm:/wasm/rain_orderbook_js_api.wasm-003e1d3e:1:469583 ❯ wasm_bindgen_futures::queue::Queue::new::{{closure}}::h74860b38de699592 wasm:/wasm/rain_orderbook_js_api.wasm-003e1d3e:1:618387 ❯ <dyn core::ops::function::FnMut<(A,)>+Output = R as wasm_bindgen::closure::WasmClosure>::describe::invoke::h7fbe4ec117d3ad35 wasm:/wasm/rain_orderbook_js_api.wasm-003e1d3e:1:618373 ❯ __wbg_adapter_34 dist/cjs/js_api.js:228:10 ❯ real dist/cjs/js_api.js:213:20 ❯ node:internal/process/task_queues:140:7 ❯ AsyncResource.runInAsyncScope node:async_hooks:206:9 This error originated in "test-js/js_api/order.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should fetch multiple orders from different subgraphs". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: Error: missing field `pageSize` ❯ module.exports.__wbindgen_throw dist/cjs/js_api.js:811:11 ❯ wasm_bindgen::throw_str::h111e4f9d3cd59f2a wasm:/wasm/rain_orderbook_js_api.wasm-003e1d3e:1:622185 ❯ wasm_bindgen_futures::future_to_promise::{{closure}}::{{closure}}::he448faefcf4baa09 wasm:/wasm/rain_orderbook_js_api.wasm-003e1d3e:1:200339 ❯ wasm_bindgen_futures::queue::QueueState::run_all::h5ef90423af5e5f2a wasm:/wasm/rain_orderbook_js_api.wasm-003e1d3e:1:469583 ❯ wasm_bindgen_futures::queue::Queue::new::{{closure}}::h74860b38de699592 wasm:/wasm/rain_orderbook_js_api.wasm-003e1d3e:1:618387 ❯ <dyn core::ops::function::FnMut<(A,)>+Output = R as wasm_bindgen::closure::WasmClosure>::describe::invoke::h7fbe4ec117d3ad35 wasm:/wasm/rain_orderbook_js_api.wasm-003e1d3e:1:618373 ❯ __wbg_adapter_34 dist/cjs/js_api.js:228:10 ❯ real dist/cjs/js_api.js:213:20 ❯ node:internal/process/task_queues:140:7 ❯ AsyncResource.runInAsyncScope node:async_hooks:206:9 This error originated in "test-js/js_api/vault.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "should fetch multiple vaults from different subgraphs". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Process completed with exit code 1.

Process completed with exit code 101.

The following actions use a deprecated Node.js version and will be forced to run on node20: DeterminateSystems/magic-nix-cache-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: DeterminateSystems/magic-nix-cache-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: DeterminateSystems/magic-nix-cache-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: DeterminateSystems/magic-nix-cache-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: DeterminateSystems/magic-nix-cache-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: DeterminateSystems/magic-nix-cache-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: DeterminateSystems/magic-nix-cache-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: DeterminateSystems/magic-nix-cache-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: DeterminateSystems/magic-nix-cache-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: DeterminateSystems/magic-nix-cache-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/