chore(streaming): Add 5000ms delay to ox_lib streaming requests

[jnccloud]

Description

Adjusts default timeout to 5s instead of the default from ox_lib. Some assets don't load in time and break scripts due to this. I would imagine worse for add-on assets. I also do not believe the default in ox_lib is working as intended.

Example from qbx_jewelry:

Checklist

• I have personally loaded this code into an updated Qbox project and checked all of its functionality.
• My pull request fits the contribution guidelines & code conventions.

[solareon]

Is there a reason that default timeout of 500 is not enough?

[jnccloud]

Is there a reason that default timeout of 500 is not enough?

Its stemmed from this topic https://discord.com/channels/1012753553418354748/1192610368195932170

But it has caused issues for players with less than ideal setups. Especially add-on assets seem to make this worse. But the most common occurrence has been in qbx_jewelry loading particle effects. I had realized I already increased to 5s on my fork of newsjob so was just pushing it upstream.

[jnccloud]

Added more details to the description and a pic of why I made this PR.

[BerkieBb]

Well the reason it fails to load in time is really because it's either badly optimized or your pc is slower, but this can be adjusted to accomodate for both

[jnccloud]

Well the reason it fails to load in time is really because it's either badly optimized or your pc is slower, but this can be adjusted to accomodate for both

I agree this user may have a slower PC but that shouldn't break a script. In the cases I've seen this happen (as you can see in the screenshot) - ox_lib only waited for 6ms. Its vanilla up to date code in these instances, so it doesn't make sense to me why ox didn't wait the default 500ms

[BerkieBb]

Well the reason it fails to load in time is really because it's either badly optimized or your pc is slower, but this can be adjusted to accomodate for both

I agree this user may have a slower PC but that shouldn't break a script. In the cases I've seen this happen (as you can see in the screenshot) - ox_lib only waited for 6ms. Its vanilla up to date code in these instances, so it doesn't make sense to me why ox didn't wait the default 500ms

It didn't wait 500ms because of how the timeout is made, the timeout counts up on every tick and a tick can be faster than 1 ms.