I didn't test it locally, my build is failing. Hopefully I can grab artifacts from CI and test it.

Perfect, I was able to build locally with --stamp flag. This PR fixes the issue, verified locally.

@nvborisenko can you build selenium manager locally? That's the big difference between stamp and not stamp. @p0deje this is probably why we had it set that way in CI?

I remember --stamp flag takes pre-build selenium manager, which allowed me to build modified C# code to verify my changes. Please ping me in chat, I will share all details you need about how build process works on my environment.

@titusfortner Looking at https://github.com/SeleniumHQ/selenium/actions/runs/5942888108/job/16117259011?pr=12591 - this doesn't seem to be related to Selenium-Manager. @nvborisenko Did you get the same error locally?

Probably we should hold this and see if it is needed after merging #12614? What do you think, @nvborisenko?

@diemol @jimevans
#12614 is merged, but I don't see protection of SendData method from concurrent use. There is still possibility to execute this method from different threads which leads to unpredictable behavior.

I think we should adopt this PR and move the protection to new WebSocketConnection class (or layer upper to DevToolsSession class?).

Ok, I adopted it with the latest trunk. This PR is ready for review.

These failures have been determined to be an issue with how we are building the alert page for the test server, so I'm going to merge without these passing.