Skip to content

Implement websocket API #290

Implement websocket API

Implement websocket API #290

Triggered via pull request March 27, 2026 00:49
@afsalthajafsalthaj
synchronize #83
web_socket
Status Failure
Total duration 13m 3s
Artifacts 17

ci.yaml

on: pull_request
Matrix: test-node-compat
Matrix: test-runtime
publish
0s
publish
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 18 warnings
Failed Test: runtime::fetch::fetch_redirects
runtime::fetch::fetch_redirects: error while executing at wasm backtrace: 0: 0x987a2a - fetch.wasm!abort 1: 0x97ee96 - fetch.wasm!std::sys::pal::wasi::helpers::abort_internal::h6ac5767e1b644f6d 2: 0x9771d4 - fetch.wasm!std::process::abort::h915eac6d11016973 3: 0x977250 - fetch.wasm!__rustc[16f1505adc47261a]::__rust_abort 4: 0x977004 - fetch.wasm!__rustc[16f1505adc47261a]::__rust_start_panic 5: 0x977027 - fetch.wasm!__rustc[16f1505adc47261a]::rust_panic 6: 0x981009 - fetch.wasm!std::panicking::panic_with_hook::h3ce0fb6586d9aef9 7: 0x97f365 - fetch.wasm!std::panicking::panic_handler::{{closure}}::h2b701c2592fa9d13 8: 0x97733f - fetch.wasm!std::sys::backtrace::__rust_end_short_backtrace::h736755c36d5f6f42 9: 0x977333 - fetch.wasm!__rustc[16f1505adc47261a]::rust_begin_unwind 10: 0x997957 - fetch.wasm!core::panicking::panic_fmt::h69ffce77273aac9b 11: 0x464355 - fetch.wasm!fetch::internal::call_js_export_internal::{{closure}}::{{closure}}::{{closure}}::he23abb6edaebece9 12: 0x4bc4a2 - fetch.wasm!<core::pin::Pin<P> as core::future::future::Future>::poll::hff449d6ff77d52d7 13: 0x4d13ac - fetch.wasm!<rquickjs_core::context::async::future::WithFuture<F,R> as core::future::future::Future>::poll::h21f9c8e6a8f920ee 14: 0x44a41f - fetch.wasm!fetch::internal::call_js_export_internal::{{closure}}::h4a707e665e334910 15: 0x44a198 - fetch.wasm!fetch::internal::call_js_export::{{closure}}::h1853b7a4057153b6 16: 0x37a9b0 - fetch.wasm!<fetch::Component as fetch::bindings::Guest>::post_with_redirect::{{closure}}::ha76dabf812a6cd96 17: 0x37a4c9 - fetch.wasm!<futures_concurrency::future::join::tuple::Join2<A,B> as core::future::future::Future>::poll::h7afdfe7be893e700 18: 0x451789 - fetch.wasm!fetch::internal::async_exported_function::{{closure}}::h0a4495c2e0504469 19: 0x64438 - fetch.wasm!async_task::raw::RawTask<F,T,S,M>::run::hc75f902225eb082e 20: 0x289e3e - fetch.wasm!async_task::runnable::Runnable<M>::run::h616f2d575bad9aed 21: 0xc2e93 - fetch.wasm!wstd::runtime::block_on::block_on::h29950db89b1052e5 22: 0x4506f0 - fetch.wasm!fetch::internal::async_exported_function::h06e4c549200ca604 23: 0x3ad59f - fetch.wasm!<fetch::Component as fetch::bindings::Guest>::post_with_redirect::heb7cb70309ebebf2 24: 0x3b8dac - fetch.wasm!fetch::bindings::_export_post_with_redirect_cabi::hda7596fc4848be0b 25: 0x3ba503 - fetch.wasm!post-with-redirect note: using the `WASMTIME_BACKTRACE_DETAILS=1` environment variable may show more debugging information: wasm trap: wasm `unreachable` instruction executed - No trace available
test-runtime (2)
Process completed with exit code 101.
build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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/
test-runtime (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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/
test-node-compat (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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/
test-node-compat (0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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/
test-node-compat (7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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/
test-node-compat (5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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/
test-node-compat (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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/
test-node-compat (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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/
test-node-compat (6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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/
test-other
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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/
test-runtime (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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/
test-node-compat (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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/
test-runtime (5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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/
test-runtime (6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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/
test-runtime (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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/
test-runtime (8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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/
test-runtime (7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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/
test-runtime (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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/

Artifacts

Produced during runtime
Name Size Digest
test-node-compat-shard-0-report Expired
40.9 KB
sha256:8efd5a07993227c2c4fac1156d23cc7fe1af5b08546f3c96eaf46666daf649bf
test-node-compat-shard-1-report Expired
41.1 KB
sha256:bbf2ede7eb1723eb7ac6f92795751eada0d179facf8396f41554435b819198fa
test-node-compat-shard-2-report Expired
41.4 KB
sha256:041f5881727a8f95f348c651959fa32c29f53b834edc6bbf071a0166ed57aa75
test-node-compat-shard-3-report Expired
40.5 KB
sha256:c190c6e989aa5b082e1409b4e25879deee338815fcf94eafd759b4f9872a6da3
test-node-compat-shard-4-report Expired
40.2 KB
sha256:798469036f300839c45ca0e36118dd98b4eb211ee36fb72f30dc89e050d749bb
test-node-compat-shard-5-report Expired
40.8 KB
sha256:6c93b2163f3547c86ca4767163680418945256a35db1e299857a72e9cb9a4f79
test-node-compat-shard-6-report Expired
40.9 KB
sha256:134d009a43fe0acd1922f2a61910bd33efc54f9547d49123374b62649f68d6ff
test-node-compat-shard-7-report Expired
42.4 KB
sha256:e4c7023480d61907336559f81a72da47db5c5240f9212d566ab5773cff305b30
test-other-report Expired
4.69 KB
sha256:7a53740096e5e7abdcc68870ed55bc3df267e42300d7da3a106dc37ebf9b38cd
test-runtime-group-1-report Expired
4.46 KB
sha256:d3f3b3c92f5ce245505f2b04bade96f303a0aa84d2ee4ac663379e919dcec0a7
test-runtime-group-2-report Expired
5.12 KB
sha256:b5b567697b4607220518a0bcd19dd6997bf716514cd8b95f620d3ce07e9cf404
test-runtime-group-3-report Expired
4.06 KB
sha256:821d6c9236b7d80365ba91494163b80c1bb66734ae74cd6e2c4f56c0b2beb1c4
test-runtime-group-4-report Expired
4.06 KB
sha256:63b5530d2fa6c731d80cba42cd76f1b72ea620f43364dbafee42c3e72b98680c
test-runtime-group-5-report Expired
3.87 KB
sha256:922c9462551fa81279758e5f4f5623310f92c7da5a8f672287604c81e9ed1d46
test-runtime-group-6-report Expired
3.7 KB
sha256:66dbef97e09845aea015d19a0a1d923dedb413478f8832202f28dd379d2d0c8e
test-runtime-group-7-report Expired
3.91 KB
sha256:65fd6239985ee2c7f726973b45fdc0749a081350b6f349e8b589c8da0f2c61c5
test-runtime-group-8-report Expired
4.45 KB
sha256:bc0975673614713a7cd0b18abb18fb807af8e96713fa66b5def6eb7bbfa46ba4