Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Unidentified issue with ULX / Ulib (?) #117
Steps to reproduce
I really am not aware of any circumstances upon which this issue is presented. I am dreadfully sorry, I know that these steps can make the difference between making this issue solvable or not.
Players are able to join and leave as they normally do without console errors.
As players join and leave, an error message is presented in the console of all online players, as well as twice in the connecting player's console.
Error(s) in server console, if any
There are no errors printed in the server console.
Error(s) in player's console, if any
This message is printed twice in the client's console. This message is also printed to all other connected players when another player connects or disconnects.
Running "ulx version" in console resulted in the "Invalid command entered" message. This is very frustrating, because I JUST updated both ulib and ulx from their respective repositories not minutes before posting this. From the XGUI, I can tell that I'm running ULX v3.62, and ULib v2.63.
Thank you for taking your time to read this over, I'm sincerely overwhelmed with the possibilities of what this error could be. I again apologize for not presenting concrete steps, but that's because I really don't know how to reproduce the error. My list of addons is below.
If there's any other information I can provide, please let me know and I will be more than willing to answer any questions.
I just looked at line 464 and it's using the same function as before (table.Empty()), which is a basegame function. This doesn't make sense to me as to why it is still erroring. I assure you that I am up-to-date. (I still can't believe that I hadn't updated since May 2015)
I tried commenting out line 464 (table.Empty()), and I was met with this completely new error. It looks like xgui.data[datatype] is not a valid table, or does not exist.
Update: I have managed to subside the original (and subsequent second) error message after changing THIS:
An extremely minor change, but a welcome one. I do not know about any impact that this may have, but I will update this as it continues. For now, I will consider this problem closed.
Thank you for your help :)
I've seen this issue pop up long ago, but I can't remember if I ever figured anything out relating to it. The most likely cause is that the server is trying to send data down to users before their XGUI client code is fully initialized, which is likely a bug on my end in any number of spots. That doesn't quite fully explain why the error will show up for everybody, though...
Your fix will definitely suppress the error, but without knowing what data might be missing (it's likely the data gets resent right away). I'm going to reopen this issue for my own tracking.
If you don't mind, you can try adding an else clause to dump some additional data for us to look at. Something like this should work:
@RealityIsnt Any further news on this issue? There's a very very small chance that I changed something that may solve this issue (latest commits on ulib/ulx master).
.. I'm also suspecting it could have been a temporary autorefresh issue- did you happen to edit any ULX-related files for any reason, and did you make sure to run a changelevel after applying updates?