-
Notifications
You must be signed in to change notification settings - Fork 1
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
Getting a closed socket error when running specs #18
Comments
@jwoertink I ran the whole spec suite now, and didn't see an issue. @derevnjuk any ideas? |
@jwoertink does it fail only on the |
oh, do I need to remove |
Just re-ran the spec and I got an email
|
Ran again, and it all passed... Could have been a fluke? Maybe the CI was having a Monday? 🤷♂️ I won't worry too much about it for now, but let me know about the |
@jwoertink you can use xss instead of dom_xss. We found an issue with scans longer then 10 minutes, I'm looking into it, we need to add a ping to our servers otherwise we decide the repeater is down. @derevnjuk noticed this behavior |
Fixed via: ecb8f52 |
When I run this spec in Lucky, I'm getting a "Closed socket" error
This is running on the latest release, but maybe I'm missing a setup somewhere since the repeater moved to Crystal?
The text was updated successfully, but these errors were encountered: