-
Notifications
You must be signed in to change notification settings - Fork 33
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
Could not perform discovery errors #111
Comments
@tgod009 I have seen this error on recent Neo4j JS driver. Can you please try using the Neo4j driver directly? Does it work? |
@jasperblues finally got around to trying with the neo4j driver directly and it worked. Any ideas why that is? |
@tgod009 are you able to share a sample where it works directly but not with drivine? That would be much appreciated and should certainly lead to a solution. |
I just initalized the driver in my service file and called the session like so
|
And the same thing does not work for you drivine @tgod009 ? |
Running Drivine like this throws the routing table error
|
Here's what I did to make it work:
@Transactional()
async createApp(name: string): Promise<void> {
const query = new QuerySpecification()
.withStatement('Merge(a:Application {name: $appName})')
.bind({appName: name});
return this.persistenceManager.execute(query);
} ^-- Note that the params are slightly different. Since we bind name parameters we supply the name. Final StepModify the it('should create an app', async () => {
await repo.createApp("foobar")
}); The test passes. If you want to see the result in the DB, at the top of that file change the following: RunWithDrivine({rollback: false}); <-- change rollback to false If you follow the approach above, does it work for you? The may be an issue but the above works for me. |
That's with the sample application? |
No, I just added it to Drivine directly. You can clone that repo, create an env file, then run the tests. Run this gist for most tests to pass: https://gist.github.com/jasperblues/7a6e774090c9ef0f18c44920b48b6b23 There are two tests that need additional setup steps. Don't worry about those, just add the code above and let me know what happens with your Neo4j server. If it works - it was a setup issue. If it does, its something environment related. I was going to add to the sample app, but I think I need to freshen dependencies. (Will do shortly). |
I gave it try and I got the same error using my db info
|
Side note not sure if this effects it but I'm using Aura not a local DB with the encrypted url |
@tgod009 I will see if I can reproduce with Aura. |
Not sure if this was causing it but I did just notice that I was using the non encrypted protocol |
If you can try with both and compare results that would be great. This is puzzling! |
Code that's throwing error:
The text was updated successfully, but these errors were encountered: