Jupiter losing IRC connection once servers die/disconnect

[fffreak9999]

Attempted with 2 Game Servers running,
If one of the servers that Jupiter is connected to dies (is killed), Jupiter disconnects from IRC.
Also Jupiter hangs if one server it is set to connect to isn't running.
This only happens when running on Linux (Ubuntu 19.10 is what I am using).

This does not occur with the last provided Windows Release, as it ignores servers it cannot connect to, and if a server disconnects/dies it continues to post in the IRC channel.

[JAJames]

This should be resolved when sockets are refactored to actually connect asynchronously.

In the meantime, a workaround to mitigate the issue is to use RenX.Listen to have the game servers connect to Jupiter (instead of Jupiter connecting to the game server), and to then relay the traffic further up to the server list using RenX.Relay.

Note that the issue can resurface using the above workaround if RenX.Relay itself then fails to connect to the upstream server list bot, since that connection also has the same issue with Jupiter's socket implementation using a blocking connect(). This workaround also requires that the bot be hosted on the same IP address as the game server, or that the node hosting the bot proxy traffic to/from the game server, which currently would have to be configured outside of the scope of Jupiter.