Files
RobustToolbox/Robust.Shared/Network
metalgearslothandGitHub 5a83ab127e Try to make connection failure msg useful (#6743)
Right now we just get an aggregateexception of IPV4 + IPV6 and roll the dice on which exception to use. The issue is if we get a generic "no response from remote host" because no IPV6 for example it can bulldoze an actually useful exception log. I would wager 90% of the time this is why connection messages aren't being useful because IPV6 is failing fast and being picked for the first exception but I could also be wrong.
2026-07-11 21:20:48 +10:00
..
2024-09-29 00:29:02 +02:00
2022-01-16 15:08:10 +01:00
2026-07-07 13:59:02 +10:00
2023-12-13 00:06:00 +01:00
2023-11-28 19:10:30 +11:00