mirror of
https://github.com/esx-framework/esx_core.git
synced 2026-08-29 17:28:53 +00:00
Selt
eaf0db6c5e
promise.state is a number, not a string - the runtime defines PENDING as 0 and Citizen.Await tests against 0 as well. Comparing it to "pending" is therefore always false and the documented 15 second timeout never rejects anything. When the other side never answers, Citizen.Await blocks the calling coroutine for good. Measured on artifact 25770 with the real 15 second delay: never answers, current guard -> state 0, not rejected, await never returns never answers, fixed guard -> state 0, rejected, await returns the timeout answers after 1s, fixed guard-> state 3, untouched, await returns normally Nothing inside esx_core calls AwaitServerCallback or AwaitClientCallback, so no core behaviour changes.
ESX Legacy
Discord - Website - Documentation
Want more resources? You can browse the Cfx.re Releases board for more!
ESX is the leading framework, trusted by over 12,000 communities to provide the highest quality roleplay servers on FiveM
💗 Supporters
Interested in helping us? Take a look at our patreon
| We would like to sincerely thank the following donors who helped fund the development of ESX. |
|---|
| Mohamad Buhamad - Michael Hein - RoadToSix - Montree Narathong |
| Saydoon - Muhannad alyamani - iSentrie - Wecity - Samuel Nicol |
| Kyle McShea - Artin - Mathias Christoffersen - Jaylan Yilmaz - Callum |
| CONGRESS KW - Michael Hein - Smery sitbon - daZepelin - CMF Community |