question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Could not connect to the playwright process

See original GitHub issue

Describe the bug I have a working test scenario using your docker image, running robot. The same setup on a differen docker host leads to error messages

Could not connect to the playwright process

and

<_InactiveRpcError of RPC that terminated with:
	status = StatusCode.UNAVAILABLE
	details = "failed to connect to all addresses"
	debug_error_string = "{"created":"@1608286023.662143927","description":"Failed to pick subchannel","file":"src/core/ext/filters/client_channel/client_channel.cc","file_line":4165,"referenced_errors":[{"created":"@1608286023.662136260","description":"failed to connect to all addresses","file":"src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":397,"grpc_status":14}]}"
>

Just in case this could be somehow related to IPv6: The working docker host has a ipv6 stack (at least /proc/sys/net/ipv6 exists), the non-working docker host does not have this key, only ipv4

Can you please give some advice how to dig deeper in that issue. How can i provide more information?

Desktop (please complete the following information):

  • OS: Ubuntu 20.04, headless
  • Browser [chrome]
  • rfbrowser-stable:v2.4.0

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5

github_iconTop GitHub Comments

3reactions
DrVanScottcommented, Jan 19, 2021

Exporting these variables

GRRPC_TRACE=all
GRPC_VERBOSITY=debug

helped me to find out the root cause. The failing docker host had been configured to export “http_proxy” variables to the containers. grpc seems to use this proxy even for localhost. Explicitly unsetting http(s)_proxy solved the problem for me.

0reactions
aaltatcommented, Jan 21, 2021

Thank you for your investigation. I guess we can close the issue now?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Error message: Could not connect to the playwright process
This usually means that you are missing Node side dependencies for the Python where you have Robot Framework and Browser installed. Because you ......
Read more >
Error when using playwright (robotframework) - Stack Overflow
Regarding the first error you stated: Calling method '_start_suite' of listener 'Browser' failed: Could not connect to the playwright ...
Read more >
Use process in Playwright Python With Examples - LambdaTest
Learn how to use process function in Playwright Python framework for your next python automation project with LambdaTest Automation Testing Advisor.
Read more >
Browser.Playwright — RPA Framework documentation
A browser process is started headless (without a GUI) by default. ... inequal , should not be, Checks if returned value is not...
Read more >
Playwright's Process Podcast - Emily Sheehan
Playwright's Process Podcast Episode 15 'The Artist's Way' Weeks 1-4 ... The final outcome depends on factors we can't even see. ... Week...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found