AirDC++ socket connection errors are not surfaced #47

New Issue

2022-12-26T23:44:03Z

rishighan commented

2022-12-26 23:44:03 +00:00

(Migrated from github.com)

Upon app init, the websocket transport to AirDC++ is attempted and once a connection is established successfully, a bunch of event listeners are registered to listen to:

Download initialization
Download ticks
Download completion

At no point is an error with the socket ever caught and thrown. In that instance, the socket errors out and the UI crashes with a cryptic trace.

There needs to be a graceful way to handle AirDC++ socket errors.

Upon app init, the websocket transport to AirDC++ is attempted and once a connection is established successfully, a bunch of event listeners are registered to listen to: 1. Download initialization 2. Download ticks 3. Download completion At no point is an error with the socket ever caught and thrown. In that instance, the socket errors out and the UI crashes with a cryptic trace. There needs to be a graceful way to handle AirDC++ socket errors.

rishighan commented

2023-11-07 19:52:33 +00:00

(Migrated from github.com)

This will be addressed in https://github.com/rishighan/threetwo/pull/96

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: frishi/threetwo#47