You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 3, 2020. It is now read-only.
Calling #fork causes the at_exit hooks to be duplicated, which means webkit-server is shut down. This can be avoided by calling exit! in the fork block, but that requires developer involvement and knowledge. It would be good if we didn't have to do that.
The text was updated successfully, but these errors were encountered:
I'm the guy of issue #181 "I still get WebkitNoResponseError".
Just to give you guys an update: I tried the most recent HEAD of revision b4faa3a
But I still get my errors Capybara::Driver::Webkit::WebkitNoResponseError: No response received from the server., followed by Errno::EPIPE: Broken pipe messages.
This means this fix did not solve my issue with capybara-webkit.
I'll update my original issue soon if there was any change in the :webkit_debug output.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Calling #fork causes the at_exit hooks to be duplicated, which means webkit-server is shut down. This can be avoided by calling exit! in the fork block, but that requires developer involvement and knowledge. It would be good if we didn't have to do that.
The text was updated successfully, but these errors were encountered: