-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
connect ECONNREFUSED after successfully connected #2301
Comments
I definitely have run into this as well, it seems that whenever a selector returns "a lot" of things I'll run into a
It manages to get the text of the first 11 elements, but fails at the last one. |
@defusioner @dangmai this has to do with the amount of parallel requests you do to the Selenium server. There is a limitation to it and if you try to get the text of 100 elements at the same time it throws an error like this because it can't handle 100 requests at the same time. I recommend to specify the element selector better. However WebdriverIO should make sure that it doesn't run too many commands. |
This is fixed with latest version. |
The problem
Hello! I'm using webdriverio to go to the page, scrub some feeds and display them via css selectors. However, I'm seeing some strange behavior with selectors, ex.:
Have I missed some promise returns? Feels like chrome can't work with "quite big" selectors. I join my code for tests. Simply call
await scrollForNewPosts(browser);
1, 2 or more times to get the error. Thanks!Environment
Code To Reproduce Issue [ Good To Have ]
The text was updated successfully, but these errors were encountered: