Open googollee opened 3 years ago
It is so strange. Into golang version 1.16 does not detected but into 1.15 was detected race. Is broken race condition detector into new go-version?
It could be 1.16 changed the scheduler and make it not so easy to trigger. I always feel that the upgrading process of old code is not a good design. That's why I hope to do a new design directly.
That's why I hope to do a new design directly.
That's good idea
I think maybe add old version 1.13 and 1.14 into github action. What do you think about it?
Just do it.
Hey, Googol! Is it actually? sorry, i don't understand. It is so strange behaviour
I believe it's very hard to fix with the current code. As I said in https://github.com/googollee/go-socket.io/issues/456#issuecomment-837243206, I'd like to design a new way to handle upgrade properly.
Describe the bug Race condition, see https://github.com/googollee/go-socket.io/runs/2513183135?check_suite_focus=true.
To Reproduce
make test
. As it's a race condition, it's hard to reproduce it every time.Expected behavior No race condition.
Environment (please complete the following information):