🤔 interesting. It was not causing any problems on my box. I was using Go go1.21.5 + go1.21.6 darwin/arm64.
Only when I added a time.Sleep(time.Millisecond) before the second startTogether call, I can reproduce the issue.
Sorry for this.
I found a similar scenario on stackoverflow that helped to resolve the issue.
Resolves #53
🤔 interesting. It was not causing any problems on my box. I was using Go go1.21.5 + go1.21.6 darwin/arm64. Only when I added a
time.Sleep(time.Millisecond)
before the secondstartTogether
call, I can reproduce the issue. Sorry for this.I found a similar scenario on stackoverflow that helped to resolve the issue.