Plugin list request has a hardcoded 5 second timeout, fails on high latency or proxied connections

[CaptainMirage]

What are you trying to do, and what do you expect to happen?

Trying to open the plugin store and install a plugin. Expected the plugin list to load like it always has before.

What happens instead?

The plugin list fails to load with a timeout, both from the main CDN (jsdelivr) and the mirror CDN (blckbn.ch). Confirmed this is not a permissions or connectivity issue on my end. Traced it to a hardcoded 5 second timeout in js/plugin_loader.ts on the request that fetches the plugin list:

$.ajax({
    cache: false,
    url: Plugins.api_path+'.json',
    timeout: 5_000,
    ...

If round trip latency to the CDN is close to or above 5 seconds, this request fails every time even though the CDN is healthy and reachable. Confirmed with a raw curl request to the same jsdelivr URL, which succeeded with a valid TLS handshake and valid response, but took about 6 seconds round trip, already over the cutoff.

This affects anyone on a connection with real world added latency, especially proxy or VPN setups with multiple hops, or system wide transparent proxy setups (TUN mode) rather than app level SOCKS5/HTTP proxy configuration. Suggest making the timeout configurable, or at minimum raising the default, since 5 seconds is very tight for anything other than a fast direct connection.

Model format in which the issue occurs

N/A, this happens before any model is created or loaded. It is the plugin store itself failing to load.

Blockbench variant

Program, PWA, Website

Blockbench version

5.1.4

Operating System

EndeavourOS (Arch-based), Flatpak installation, linux-g14 kernel

Installed Blockbench plugins

None installed yet, this is what is being blocked

Are there any console errors?

yep

plugin_loader.ts:1032 Could not connect to plugin server: timeout {readyState: 0, ...}

[CaptainMirage]

manually patched the flatpak by bumping the number up to 20 (tho it only needed 2 or 3 more secs) and its working, tho its best to make some dynamic system for it or at least add a variable and a settings option to change it but for now i've confirmed the problem, just needs a good fix

im super busy at the moment but ill come back in a few weeks and put a PR myself if it isnt fixed by then (and please dont make it another fixed number its best to make some system to use in other places too, many thanks)

[JannisX11]

I'm planning to add a config menu for things like this. It's not gonna come out in the next weeks since it's a bigger feature, but I can increase the value for now in the next patch.

[CaptainMirage]

I'm planning to add a config menu for things like this. It's not gonna come out in the next weeks since it's a bigger feature, but I can increase the value for now in the next patch.

it would be nice to have the number bumped until the update comes out, would recommend 10 to 15, anything above might make it a bit tedious and annoying to debug any future problems, maybe even add a debug log of some kind to show its trying to connect in the console logs so if someone hits some similar problem related to the same part of the code either they can figure out whats wrong or at the very least you know what is going on with less back and forth (if they ask it in the discord or somewhere that is)

also if its in your plans and until im free it wont come out, i might do a sweep of the code see if anywhere else has something similar and make a system for all of them to dynamically change the timeout too (already have an idea for it, ill share if you wish its somewhat half baked)