theANDYM Posts

theANDYM

•Created by theANDYM on 5/2/2025 in #help

Issues with a Rust panic running workers and attempting to use `otel`

I'm having issues in an app that heavily relies on web workers; I am greeted by an almost instant issue:

============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.

Platform: macos aarch64
Version: 2.3.1
Args: ["/Users/andy/.deno/bin/deno", "run", "--allow-env", "--allow-ffi", "--allow-net", "--allow-read", "--allow-run", "--allow-sys=osRelease", "--allow-write", "--unstable-otel", "--cached-only", "--watch", "./main.ts"]

View stack trace at:
https://panic.deno.com/v2.3.1/aarch64-apple-darwin/gqvgKg-ykqB4stxqB4jtxqBw_5xqBgok5Lw4phPozigQg5pkgBg8okgB

thread 'worker-1' panicked at /Users/admin/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/deno_unsync-0.4.2/src/tokio/task.rs:62:13:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.

Platform: macos aarch64
Version: 2.3.1
Args: ["/Users/andy/.deno/bin/deno", "run", "--allow-env", "--allow-ffi", "--allow-net", "--allow-read", "--allow-run", "--allow-sys=osRelease", "--allow-write", "--unstable-otel", "--cached-only", "--watch", "./main.ts"]

View stack trace at:
https://panic.deno.com/v2.3.1/aarch64-apple-darwin/gqvgKg-ykqB4stxqB4jtxqBw_5xqBgok5Lw4phPozigQg5pkgBg8okgB

thread 'worker-1' panicked at /Users/admin/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/deno_unsync-0.4.2/src/tokio/task.rs:62:13:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Are there any known workarounds? I've been searching for a solution but haven't been able to locate one.

3 replies

DDeno

•Created by theANDYM on 2/9/2024 in #help

Headers for WebSocket client

I need to connect Deno (as a client) to a WebSocket server that requires custom headers on connection. I can't seem to find any currently supported method to accomplish this since the WebSocket API only allows for the url and protocols parameters. Is there any known best practice to accomplish this?

2 replies