Adonis
Adonis copied to clipboard
Script timeout: exhausted allowed execution time
#148 Is still very much an issue! Might be a different function though
This is a different error to the one bandaided by Sceleratis. This is a standard script timeout. Do you have any plugins? What is in your settings file?
This is a different error to the one bandaided by Sceleratis. This is a standard script timeout. Do you have any plugins? What is in your settings file?
It might have to do with the fact that our ban list is insanely big, because the line that errors is this one (We're considering just dumping the ban list in another script)
Edit: we ended up moving said ban list away from the DataStore and into the settings file, we have 2659 bans and that might the the reason why the unpack function chugs.
This is a different error to the one bandaided by Sceleratis. This is a standard script timeout. Do you have any plugins? What is in your settings file?
It might have to do with the fact that our ban list is insanely big, because the line that errors is this one (We're considering just dumping the ban list in another script)
Edit: we ended up moving said ban list away from the DataStore and into the settings file, we have 2659 bans and that might the the reason why the unpack function chugs.
I can try to implement a solution today, it might work, it might not. For you, I recommend not banning 2.6k people in the future if you can help it. What the hell? What are you daily player numbers?!
I am going to try to implement a version of table.unpack which yeilds periodically, possibly even using multithreading. This will be based off the LuaU source code if it's in there, if not I give up.
Save some people some time in finding it, but it's obviously tasty C code
https://github.com/Roblox/luau/blob/e06b5c2e28b638d31c091ca9671f0efee3f1ba51/VM/src/lbuiltins.cpp
@Expertcoderz @Sceleratis @joritochip @Mudock-Yatho If you guys have a better solution to this, let me know.
Do also bear in mind that whatever this does, which I ain't read it properly yet, might not be doing it properly?
I can try to implement a solution today, it might work, it might not. For you, I recommend not banning 2.6k people in the future if you can help it. What the hell? What are you**(r)** daily player numbers?!
We'll see in the future what that solution gives us, but we have like 4k CCU rn lol
tbh I don't think unpack should be having any issue... it's not like it would be unpacking the banlist, just returning the table for it...
Hiya, co-worker of cl1ents here
We mitigated the issue by storing the old banlist we had (the reason this issue is only happening now is because we were moving a ban list over from HD Admin) in a ModuleScript and we just gave it to the settings script instead.
The issue no longer exists. We're happy to implement any future solutions later down the line if they'd be more beneficial.
tbh I don't think unpack should be having any issue... it's not like it would be unpacking the banlist, just returning the table for it...
I doubt it's unpack, I think it was just the size of the DS. Before I cleared it I realised it was taking up about 12.6% of the allowed storage capacity on any given DS, so it wouldn't surprise me if it was literally just taking a while
It's still kind of an odd issue, even if it is because of the DataStore being insanely big, why does it decide to not work like in 1/10 cases? Roblox Luau (lowercase u, /ˈlu.aʊ/) quirks??
It's still kind of an odd issue, even if it is because of the DataStore being insanely big, why does it decide to not work like in 1/10 cases? Roblox Luau (lowercase u, /ˈlu.aʊ/) quirks??
It's possible that something related to the queue handler stuff in Adonis is looping or yielding in some way that's causing the issue (loop with no wait, basically a crash?)
Even if the datastore has 2k+ records it shouldn't be struggling to handle that. It's a lot for a human but not for modern computing.
https://github.com/Sceleratis/Adonis/issues/788
Is this still occurring?
Is this still occurring?
Can confirm this is still occurring in my game, but I have noticed that it is less common (usually 2/3 servers have the issue, previously was near 100%)
couldn't we just for loop and get the returns and then add a task.wait()
I found something that might relate to this
die
die
no die
Apparently people are having this issue again:
It's only April Fools, I'm sure they were joking
It's only April Fools, I'm sure they were joking
Lmao I didn't even realise that
Are you sure though the person getting the crash message is joking?
I've said this many times before:
Follow the ostrich algorithm.
Follow the ostrich algorithm.
i'm having this same issue rn
i'm having this same issue rn
Have you tried using the ostrich algorithm?
i'm having this same issue rn
Please factory reset the Roblox client.
i'm having this same issue rn
Please factory reset the Roblox client.
He needs to update his FTI Remote Parameters to include acceptance for all user agents regardless of SAM.