xtdb 2021-08-03 | Slack Archive

richiardiandrea03:08:44

Hi there, I have a problem in the test where crux/tx-committed? always returns false - no matter await-tx I have reduced it to have an start-node {} and everything in memory (assuming the memory store is not stateful) and after checking the latest-completed-tx and the tx id is matching... Any suggestion on how to debug? Side note - I upgraded to 0.18.0 then reverted to 0/17.1 - I am not sure though the problem was because of the upgrade

richiardiandrea03:08:59

never mind, I think I have a bug in my crux.tx/match

refset08:08:00

Is it something you'd have expected the spec conform for the match to pick up?

richiardiandrea14:08:45

No Jeremy this is probably my dumbness but thanks for asking 😄

refset15:08:28

ha, well, computers are hard 😅

ray12:08:16

I don't know if this is on topic but wondering if anyone has made a Heroku addon for Crux? I could be interested in doing it if there's nothing out there

refset12:08:35

can confirm there's nothing out there I'm aware of either! The big limitation with Heroku is the cap on local disk size and the ~daily cycling of the dynos, but for small / hobby use-cases it's probably very convenient. Semi-relatedly, I did get Heroku's JDBC backend working well once

refset12:08:37

if you've not used Clojure with Heroku before (I haven't seriously), then there might be some interesting patterns/snippets to borrow from https://github.com/kommen/datahike-heroku

ray12:08:18

No problem, I know Heroku well

👌 3

ray12:08:32

I have a build pack for tools.deps 🙂

ray12:08:20

back in the day I came close to writing an add-on for Datomic but Cognitect would not waive the license restrictions

ray12:08:39

their SPI allows you to spin up and connect AWS resources

ray12:08:20

that's how the addons to persist data all work essentially

ray12:08:19

[ I can't find anything so I'm guessing no but still though I thought it sensible to ask here ]

2021-08-03

Channels