-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Example driver code don't work for me #6
Comments
Thanks for the bug report @andreymeretsky, I've regenerated the protocol modules and added in the README of how that works, and fixed a few bugs, and got the example script working locally. Once you get it going, I'll close this issue. |
Since there is no response, I'm assuming this is now working. |
Sorry, I couldn't test it earlier. I added script which i ran for test. I start Chrome in it also. As i saw from error trace script fails by timeout :( If you want to ask more questions you can contact with me by telegram http://t.me/mouse_meretsky |
@andreymeretsky I've been able to recreate error in my Docker container (works fine locally under MacOS), will let you know how I go. |
I think the Docker Error might be that you never start Chrome. This causes it to time out while connecting to the remote debug port. This is fixed by you having Chrome running locally with --remote-debug-port=9222 as per the readme. |
I ran the example driver code and got TimeoutError
/usr/local/lib/python3.6/dist-packages/chromewhip/helpers.py
As you can see in debugger there is no frameId and loaderId in params and LifecycleEventEvent constructor needs it!
Is that an error in chromewhip or i understand something wrong?
This error also arrised when using docker and http api.
The text was updated successfully, but these errors were encountered: