Can we build visualizations for the observability data (at https://<host>:<port>/metrics) into the UI?
There are no visualizations that would be useful for local
Many of the cloud visualizations can’t be ported over because they are collected by the Cloud infrastructure
Should it be possible to have an object type in a named tuple?
Now it triggers an ISE
I have an edgedb database running in a docker container (edgedb v2) and did a dump using edgedb-cli v2.6. When i try to restore this dump into a docker container running the last edgedb image with edgedb-cli v3.4, the database is not running properly, incorrect query results (sort orders). When i restore the same dump in dev running edgedb v3, it’s working properly. Any ideas why restoring a db in docker gives different results?
Following up to find out the query
User wanted to note that using Rust would speed up their startup time and their CI tests as a result, since they have to run EdgeDB in CI for their tests.
Plan to rewrite I/O layer of EdgeDB in Rust, but rewriting the compiler will be far down the road.
There are other optimization strategies we can do short of rewriting the compiler in Rust that could be helpful. We are confident we can improve 2x with what we have now (probably not in Rust).
Performance is becoming more of a priority. Gradually rewriting things in Rust on the server.
Maybe give it a pre-bootstrapped snapshot with a cached data directory. Next CI run, use the cached data directory.
What sort of CI are you using? (May be able to help in setup-edgedb by supporting data cache to make starts faster)
Open an issue in setup-edgedb
In our docs, we say that JSON cannot be cast to a tuple. I can confirm this is the case in the CLI REPL, but a user has discovered it is possible via HTTP using this query: {"query":"with data := <tuple<a:str,b:str>><json>$data, select data;", "variables":{"data":{"a":"eee","b":"smstr"}}} I’m able to confirm that it does, in fact, return what looks like a named tuple. I ran this: curl --data '{"query":"with data := <tuple<a:str,b:str>><json>$data, select data;", "variables":{"data":{"a":"eee","b":"smstr"}}}' --header 'Content-Type: application/json' http://localhost:10757/db/edgedb/edgeql
and got back this: {"data":[{"a" : "eee", "b" : "smstr"}]}
Does the documentation need to be updated, or is this a bug?