questdb: web console UI grid not showing results
Describe the bug
simply as per title, any query on the editor show the number of columns of the result but the grid in the UI is always empty.
Apparently the component has been updated in 3068
To reproduce
open web console UI write a “select * from tableName” the grid shows no results
the javascript of the UI fails with:
Uncaught TypeError: Cannot read properties of undefined (reading 'digest')
at qdb.js:2:913132
at qdb.js:2:913264
at qdb.js:2:913268
Expected Behavior
the table should show result
Environment
- **QuestDB version**: 7.1
- **OS**: Any
- **Browser**: Any
Additional context
No response
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 2
- Comments: 16 (8 by maintainers)
@bluestreak01 crypto-api is usable only in a “secure context”: https://developer.mozilla.org/en-US/docs/Web/API/CryptoKey
which means, any local installation which is not operated behind a https-proxy or the like will face the issue.
i have tested with safari, firefox, google-chrome against http://localhost:9000: all the same result of what @tolap22 reported. https://demo.questdb.io works like a charm.
fixed in https://github.com/questdb/questdb/releases/tag/7.1.1
This issue is fixed with the new release, 7.1.1. Link: https://github.com/questdb/questdb/releases/tag/7.1.1
7.1 has improved grid features, so that’s why we only have this issue in 7.1. As a temporary workaround, you could downgrade to 7.0.1. Alternatively, you can try running a local HTTP proxy, so that Web Console’s URL is
localhost
or127.0.0.1
.Looks like the issue stands true when Web Console is accessed over plain HTTP (no SSL/TLS) and URL other than
127.0.0.1:port
orlocalhost:port
(these two are considered an exception in the “secure context” requirement).I have same problem on all of our tests environments after update from 7.0.1. We use docker version. Same problem on fresh install and upgrade from 7.0.1
Download result as CSV works so there is problem with web console UI. Same problem on firefox and chrome
EDIT:
I also try bare-metal version, same error