Skip to content
This repository was archived by the owner on Sep 3, 2021. It is now read-only.

install apollo-server-errors and import ApolloError from it in federation.js #439

Merged
merged 1 commit into from
May 16, 2020

Conversation

wworrall
Copy link
Contributor

Fix issue #420

@wworrall
Copy link
Contributor Author

wworrall commented May 16, 2020

Hi @johnymontana, I was wondering whether you could help.. The above CircleCi test is failing but on inspection it seems to be a database connection error. Would you be able to shed any light on this?

Copied from here:

✖ before hook GraphQL error: Failed to connect to server. Please ensure that your database is listening on the correct host and port and that you have compatible encryption settings both on Neo4j server and driver. Note that the default encryption setting has changed in Neo4j 4.0. Caused by: connect ECONNREFUSED 127.0.0.1:7687

  Ran 1 test file out of 1 for job 1 of 1

  1 hook failed

  before hook

  /home/circleci/project/test/integration/gateway.test.js:39

   38: 
   39: 
   40: 

  GraphQL error: Failed to connect to server. Please ensure that your database is listening on the correct host and port and that you have compatible encryption settings both on Neo4j server and driver. Note that the default encryption setting has changed in Neo4j 4.0. Caused by: connect ECONNREFUSED 127.0.0.1:7687

@johnymontana
Copy link
Contributor

Thanks @wworrall! Regarding the failing test, it seems the Gateway integration tests are a bit flaky on CircleCI, rerunning the failed workflow usually does the trick 🙃 It's on my list of things to fix :-)

@johnymontana johnymontana merged commit f6832de into neo4j-graphql:master May 16, 2020
@johnymontana
Copy link
Contributor

@wworrall @emregency I went ahead and published this in v2.14.1-alpha.2 with the @next tag, which you can install with

npm install neo4j-graphql-js@next

for testing. I'll cut a proper release sometime next week.

@emregency
Copy link

@johnymontana This works. Thanks.

P.S.: Fragments still do not work with custom @cypher statements ref. #392

@wworrall
Copy link
Contributor Author

@johnymontana thanks for merging and for your continued efforts.

@johnymontana
Copy link
Contributor

Thanks folks! This fix is now published in v2.14.2

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants