waha
waha copied to clipboard
[BUG] Possible 2 sessions with one name in Runtime
In really rare circumstances, it's possible to end up with two sessions (either browser in WEBJS or websocket connections in NOWEB)
We need to prevent this from happening by some looking mechanism inside the engine itself, so we 100% sure it can not happen due to concurrent internal events (it's not possible right now to achive via API, because we already have locks there)
+1