You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version: Deno 2.2.11
While migrating from traditional logs to OpenTelemetry, I encountered a panic when using --unstable-otel alongside hono/client for RPC.
🧪 Reproduction steps:
Using this code snippet:
import { hc } from 'hono/client';
export const client = hc<AppType>('http://localhost:1338/');
The app panics when making any request using client.*() if OpenTelemetry is enabled:
deno run --unstable-otel ...
This panic occurs regardless of:
Whether the request comes from an SPA, SSG, or a static pre-compiled client.
Runtime environment (local or deployed).
✅ Temporary fix:
Removing --unstable-otel resolves the issue and the app runs normally.
Let me know if logs or a minimal reproduction repo would help—happy to provide!
The text was updated successfully, but these errors were encountered:
mirairoad
changed the title
Deno Panic when using --unstable-otel + hono/client RPC #panic #bug #deno #otel
Deno Panic when using --unstable-otel + hono/client RPC
Apr 25, 2025
Version: Deno 2.2.11
While migrating from traditional logs to OpenTelemetry, I encountered a panic when using --unstable-otel alongside hono/client for RPC.
🧪 Reproduction steps:
Using this code snippet:
The app panics when making any request using client.*() if OpenTelemetry is enabled:
This panic occurs regardless of:
Whether the request comes from an SPA, SSG, or a static pre-compiled client.
Runtime environment (local or deployed).
✅ Temporary fix:
Removing --unstable-otel resolves the issue and the app runs normally.
Let me know if logs or a minimal reproduction repo would help—happy to provide!
The text was updated successfully, but these errors were encountered: