[Bug] HTTP timeout / request failure fetching ListenBrainz sitewide artist stats #2155
Replies: 1 comment 1 reply
|
I'm gonna chalk it up to chatgpt hallucination, but your statement that "Nuclear's underlying HTTP client enforces a strict request timeout" is completely untrue, in fact there's no timeout at all for most requests. It's your internet connection. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Nuclear fails on startup/dashboard load when attempting to fetch sitewide artist statistics from ListenBrainz, throwing the following error:
GET https://api.listenbrainz.org/1/stats/sitewide/artists?count=50&range=week failed: error sending request for url (https://api.listenbrainz.org/1/stats/sitewide/artists?count=50&range=week)
Root Cause Analysis:
The endpoint (api.listenbrainz.org/1/stats/sitewide/artists?count=50&range=week) is operational, but backend aggregation causes significant response latency (often taking several seconds to complete the request).
Because Nuclear's underlying HTTP client enforces a strict request timeout, the connection is dropped before the heavy JSON payload finishes downloading.
Suggested Fix:
Increase the HTTP request timeout limit specifically for the ListenBrainz dashboard plugin.
Add async retry logic or graceful error handling so a slow stats response doesn't surface a blocking UI error message.
All reactions