You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Docker image runs playwright version 1.4.2, i know that the problem is not docker image because when vscode debugger attached, I can see the playwright launch the server and pass it on from this line.
Also, I have managed to connect to the chromium-browser in docker running V 1.4.2 from 1.3.0 client. so I am assuming that the problem is not docker image.
Thanks!
The text was updated successfully, but these errors were encountered:
Could it be that you rely on the specific wsEndpoint format or the shape of the remote protocol?
With 1.4 we switched to the new non-compatible protocol compared to 1.3. You can read about it in the "New Client / Server Wire protocol" section of release notes.
Note that if you launchServer with 1.4 and connect with 1.4 by passing wsEndpoint directly, it is supposed to work.
To help debugging, could you please run your server or client with DEBUG=pw:channel* and provide the logs?
i have had a chance to look into it today, the problem was not with playwright nor docker image, it was my mistake of using docker local registry wrongly, sorry for any inconvenient.
Context:
After version 1.4.x the
browserType.connect()
never get resolved, it appears that the promis in this line never get resolved.For remote browser, I am using this docker repo.
Docker image runs playwright version 1.4.2, i know that the problem is not docker image because when vscode debugger attached, I can see the playwright launch the server and pass it on from this line.
Also, I have managed to connect to the chromium-browser in docker running V 1.4.2 from 1.3.0 client. so I am assuming that the problem is not docker image.
Thanks!
The text was updated successfully, but these errors were encountered: