3 ms·

Tailscalar here. There were a few things going on with that issue you mentioned; one of them is the way the wrapper library was written, the other was with som

Tailscalar here. There were a few things going on with that issue you mentioned; one of them is the way the wrapper library was written, the other was with some stuff in the GUI client that was happening on a background goroutine but shouldn't have been. That should be fixed in the current stable release. As for the Windows client in general, it is going to be receiving a lot of love over the next few months!

jchw 4y ago
I see; I need to update the client on one of my machines. I appreciate the heads up, as it is quite frustrating to get it to start sometimes. Thanks! I'll have to check out the bug sometime, but it sounds like it's just bad luck with goroutine scheduling and the order things execute in, in a goroutine that isn't locked to a thread. I can see it going unnoticed on older versions of Go (especially prior to weirder things like usermode preemption.)
- bradfitz 4y ago
  What bug are you thinking of? Got a GitHub issue link?
  - jchw 4y ago
    I believe it might be this one. https://github.com/tailscale/tailscale/issues/4133 https://github.com/tailscale/tailscale/issues/4133 That said, I'm not near the computer where I have it occur right now to check.
    - bradfitz 4y ago
      That's hopefully fixed now in 1.34.0+. We'll see!