This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-18
Channels
- # announcements (6)
- # aws (1)
- # babashka (47)
- # beginners (50)
- # calva (65)
- # cider (4)
- # clj-commons (17)
- # clj-kondo (44)
- # clojure (150)
- # clojure-europe (41)
- # clojure-nl (4)
- # clojure-spec (1)
- # clojure-sweden (4)
- # clojure-uk (6)
- # clojurescript (15)
- # clr (1)
- # conjure (1)
- # core-async (7)
- # cursive (5)
- # datomic (12)
- # events (2)
- # fulcro (17)
- # graphql (12)
- # introduce-yourself (1)
- # jackdaw (5)
- # jobs (2)
- # lsp (52)
- # malli (5)
- # meander (3)
- # minecraft (2)
- # missionary (2)
- # off-topic (10)
- # other-languages (9)
- # reitit (9)
- # remote-jobs (1)
- # ring (8)
- # rum (7)
- # shadow-cljs (9)
- # sql (2)
- # tools-deps (20)
- # xtdb (12)
I have a document {:xt/id "
that only shows up with (tx/entity ,,,)
, but not with (tx/q db {:find [?e], :where [[?e :xt/id]]})
.
The weird thing is if I save a new document with a different username, for example foo.bar
the code will work.
Any ideas on how to debug this?
Hi 🙂 I agree this looks weird...are you running everything in-memory? If you can distil a repro and upload it somewhere then I would certainly like to investigate it. Alternatively, if you have time and interest, I would be very happy to pair on this tomorrow if there's a convenient time (feel free to DM me!)
Thanks, that's useful to know. Were both the entity
and q
calls you mentioned running against the same db
?
So if I drop the postgres database, and recreate it from scratch, the code is working fine and as expected. I’ve somehow gotten the database into an invalid state. I took a backup of the broken sql database if you want to see it. However, while it is a test database with only test data, some of the PII are real so I would not be comfortable sharing it publicly.
Hmm 😕 Well, if you would be more comfortable emailing it encrypted or something, perhaps we could try that. I could even arrange for us to sign an NDA or similar and promise to delete the files when we're done (one way or the other)
Just in case anyone ever comes across this again - it turned out to be the same issue as https://github.com/xtdb/xtdb/issues/1683 (which got fixed)
Currently deployed an XTDB node using the juxt/xtdb-standalone-rocksdb docker image. It is working great, yet the logging inside the container is at DEBUG which is generating a massive amount of noise. Anyone know how to change this log level for the node running in the docker container? (The docs talk about how to change in the REPL, but not clear how to do this for the node running via docker)
Hey @U025VPS4R7U I just pasted the Q&A here https://discuss.xtdb.com/t/modifying-logging-in-the-docker-image/65 (hope you don't mind!) - but feel free to follow-up wherever's easiest