Closed gauthier-voron closed 1 year ago
Did not manage to reproduce.
Could be caused by race condition on run.Service
exit sequence where a run.jobExit
message could be sent after the net.Connection
has been closed, which would panic
.
Fixed in 6b43da9c1594db1acd7537d2e56d36fb3b97e69d
On setups with high latency and small bandwidth, running a command that fails (e.g.
rm <file>
where<file>
does not exist) makes the silk server crashes.