-
Notifications
You must be signed in to change notification settings - Fork 471
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
JSTree Error: Failed to execute 'querySelector' on 'Element' #425
Comments
Do you have the output of the server-side console? Can you post it please? And when does it throw the errors? On initial display of the tree without opening anything on key level? OR after clicking of the server entry inside the key (with the red redis logo) Or opening the keys below it... |
Nothing shows up in the server-side logs, just browser console. Here is the complete output from Chrome:
This appears in the console when the app first loads and if we attempt to expand the tree. If I click on the main Redis node then I am able to see server info. |
Your comment about binary data got me thinking, I deployed another test app so I could see the keys and it looks like some encrypted keys and values were written. I ran FLUSHALL and was able to get things working again. So FYI that bad keys will completely break the UI. Thanks for the assistance. |
than i reopen it - we have to do something about this kind of keys to not break the UI. |
just think about the problem - do you have any idea or preferences how binary keys should be represented in the tree view? Thanks |
When deploying Redis Commander to Pivotal Cloud Foundry I'm able to load the service details for Redis and connect, but JSTree is throwing numerous errors for the querySelector.
Clicking the refresh button or a node on the tree throws the following error:
Uncaught DOMException: Failed to execute 'querySelector' on 'Element': '#R:q-s0.redis-instance.dynamic-services.service-instance-422e5436-73b3-49d4-af9c-dc0c3b9a6809.bosh:6379:0:,O^m��RV!$�����' is not a valid selector.
The text was updated successfully, but these errors were encountered: