Skip to content

Conversation

@pe4cey
Copy link
Contributor

@pe4cey pe4cey commented Oct 8, 2018

Issue:

In a causal clustered setup when executing the :queries command, the resulting frame displays the records returned from running call dbms.listQueries on all cluster members. If the username and password used on the current session are invalid with any of the other cluster members, the frame would throw an error and cause Neo4j Browser to become unresponsive.

Fix:

Gracefully handle errors from the individual members and display the error to the user. A more detailed error message is displayed as an error row tooltip.

screen shot 2018-10-08 at 09 39 34

changelog: Fix crashing :queries frame in clustered environments when all members couldn't be reached

@vercel
Copy link

vercel bot commented Oct 8, 2018

This pull request is automatically deployed with Now.
To access deployments, click Details below or on the icon next to each push.

@oskarhane oskarhane merged commit 4284fc6 into neo4j:master Oct 8, 2018
myzero1 pushed a commit to myzero1/neo4j-browser that referenced this pull request May 17, 2019
Fix `:queries` frame so that connection errors are displayed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants