Hilariously, at no point in this patch had we started this service process
This does seem to indicate that either the tests are not really validating anything useful, or the issue was a non-issue to begin with. This patch nevertheless contains useful improvements to our tracing of registration events, so I think it's still valid.
commit02494f2de06bf6a2e970fed5699624aa95ad2cb2
authorTim Watson <watson.timothy@gmail.com>
dateTue 13 Nov 2018, 15:05 (8 years ago)
parent1cf2a29
src/Control/Distributed/Process/Node.hs+1
@@ -376,6 +376,7 @@ startServiceProcesses node = do
376376 -- loops during tracing if the user reregisters the "logger" with a custom
377377 -- process which uses 'send' or other primitives which are traced.
378378 register "trace.logger" logger
379+ void $ registryMonitorAgent
379380 where
380381 loop = do
381382 receiveWait