-
Notifications
You must be signed in to change notification settings - Fork 103
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
Error is thrown when trying to run the connector #230
Comments
Hi @jarrodek It looks like the driver is closed somewhere, based on this part of the log |
@twoplustwoone could you please reproduce this in a separate repo? Please, create a new repo in our org with this issue. |
Stumpled upon the same thing, I just took https://github.com/axios/axios and upgraded all deps to:
if you run npm run test afterwards, you will get the same error. |
Thanks @simllll Will take a look at it tomorrow and let you know |
I cloned the project, updated the dependencies as mentioned and adjust the
|
Strange, what I did besides the package.json was removing uglify from webpack config and and rmeove the comment /global toString:true/ from utils.js. I guess you did probabaly the same, what system are you running on? Maybe it's related with node 15? I will check now. as a side note, not sure if relevant, but I get a warning that safari is not found (well I'm on linux ;)): If i compare the browsers to your list, the indeed differ a lot. Could this be some hint? |
Anything I can do to help tracking this down? I believe it has something todo with my environment... |
Hi @simllll Sorry for my late response, busy week. I've been running this from my mac, here are some logs Node.js 14
Node.js 15:
Can you share a reproducible example? |
A fix has been released, can you please check if it works for you? |
@wswebcreation I bumped the Example log output from one of the failures:
Let me know if you can find any clues, thanks! |
I don't have write access to the repo so would have to open another PR but the cycle time between trying a change, opening a PR, merging to master is pretty gnarly 😅 I thought I could fix it by just bumping the version but that didn't work out. Maybe the maintainers might be up for it but ya unfortunately PRs don't run with Sauce creds until merged. It was literally just bugging me all the build indicators were red haha |
I started seeing some weird errors. The following is (truncated) exec logs.
I am not sure where exactly the problem is. I was trying to change the configuration to bare minimum, then i tried to copy the configuration from the readme file but still no luck. Regular karma tests are executed locally and on Travis. The errors start only when trying to run SL tests.
I am hoping for a help with solving this.
The text was updated successfully, but these errors were encountered: