Skip to content

Panics on network errors due to .unwrap() calls in dioxus-fullstack WebSockets #5247

@matous-volf

Description

@matous-volf

Problem

Basically #4915, but with WebSockets. For instance, I got

thread 'main' (24899) panicked at /usr/local/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/dioxus-fullstack-0.7.3/src/payloads/websocket.rs:624:22:
called `Result::unwrap()` on an `Err` value: Reqwest(reqwest::Error { kind: Request, url: "http://100.64.0.11:8000/api/subscribe_to_updates", source: hyper_util::client::legacy::Error(Connect, ConnectError("tcp connect error", 100.64.0.11:8000, Os { code: 110, kind: TimedOut, message: "Connection timed out" })) })

Environment:

  • Dioxus version: v0.7.3
  • Rust version: rustc 1.92.0 (ded5c06cf 2025-12-08)
  • OS info: Arch Linux
  • App platform: web, mobile

Questionnaire

I would like to fix and I have a solution.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions