-
Notifications
You must be signed in to change notification settings - Fork 17
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
Too many connections error #22
Comments
I think you mean chrisk's fakeweb. This is a node module. — On Fri, Jan 22, 2016 at 11:08 AM, Achilleas [email protected]
|
Haha damnit duckduckgo, sorry about that Chris. |
No worries! — On Fri, Jan 22, 2016 at 11:33 AM, Achilleas [email protected]
|
Hi,
In a project where we use fakeweb I ran into an issue when I tried to connect to Neo4j (a graph database). The gem I used to connect to it (neo4jrb) uses net-http to connect to the database and it turns out that fakeweb interfered with this in development.
I described my issues in detail here:
neo4jrb/activegraph#555 (comment)
After some back and forth between ruby versions and disabling various gems I found out that fakeweb was, in the end, the culprit in my spotty connection with the database. Since removing fakeweb from my Gemfile I haven't had any issues.
The error I received was:
Please let me know if you need any more information.
The text was updated successfully, but these errors were encountered: