Skip to content
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.

Sign up for GitHub

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

Jump to bottom

con$ping broken for v3.5 #2

Open
davidlrosenblum opened this issue Sep 11, 2020 · 2 comments
Open

con$ping broken for v3.5 #2

davidlrosenblum opened this issue Sep 11, 2020 · 2 comments
Labels
bug Something isn't working

Comments

@davidlrosenblum
Copy link
Owner

There is no db.ping() function in 3.5 - we need to use the old end point.
@davidlrosenblum davidlrosenblum added the bug Something isn't working label Sep 11, 2020
@davidlrosenblum davidlrosenblum changed the title con$ping needs broken for v3.5 con$ping broken for v3.5 Oct 20, 2020
@davidlrosenblum
Copy link
Owner Author

It is still a bit quirky - needs more work.

@davidlrosenblum
Copy link
Owner Author

davidlrosenblum commented Oct 20, 2020 •
edited
Loading

The remaining issue with ping is if the server is up, but if that database doesn't exist or is stopped, then we don't get the 404 b/c we are calling it as a cypher. So we need a simple query to hit the get_wrapper, where we can catch the status code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@davidlrosenblum