Bug in console when running through Pterodactyl
Nesroht opened this issue · comments
When running MultiAdmin through pterodactyl the server functions and logfiles seem to indicate that nothing is wrong
[17:30:40] If you are 100% sure that the server is working, can be accessed from the Internet and YOU WANT TO MAKE IT PUBLIC, please set up your email in configuration file ("contact_email" value) and restart the server. [17:30:40] Initializing generator... [17:30:40] Spawning items... [17:30:42] The scene is ready! Good luck! [17:30:42] Waiting for players.. [17:36:24] Refreshed public key of central server - key hash not changed. [17:42:24] Refreshed public key of central server - key hash not changed. [17:48:25] Refreshed public key of central server - key hash not changed.
But looking at the console output in the pterodactyl panel gives a mess:
[17:42:24] Value -1 exceeded buffer height 0. at System.TermInfoDriver.SetCursorPosition (System.Int32 left, System.Int32 top) [0x00021] in <3833a6edf2074b959d3dab898627f0ac>:0 at System.TermInfoDriver.set_CursorTop (System.Int32 value) [0x00015] in <3833a6edf2074b959d3dab898627f0ac>:0 at System.ConsoleDriver.set_CursorTop (System.Int32 value) [0x00000] in <3833a6edf2074b959d3dab898627f0ac>:0 at System.Console.set_CursorTop (System.Int32 value) [0x00000] in <3833a6edf2074b959d3dab898627f0ac>:0 at MultiAdmin.Server.Write (MultiAdmin.ColoredMessage message, System.Int32 height) [0x0005a] in <36b28ec5663646cba999b1195af37bff>:0
Looking at the source code it doesnt seem to be so much an error as a catching of an exception being pushed to console.
If it has any implication on the issue this is Ubuntu 16.04 running 0.7.12 Panel and 0.6.11 Daemon of pterodactyl.io
I'm working on a ton of changes to the input system, including fully re-writing the input handling. Hopefully this should resolve many issues, everything related to console size has been put in a try catch loop with the output being ignored (I may in the future change this so that some errors are printed?)
Closing because this should be fixed, please re-open if you find the latest test version available on the Discord still has this issue, the release #206 is planned to happen soon.