This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-12
Channels
- # aleph (3)
- # announcements (15)
- # architecture (6)
- # babashka (35)
- # babashka-sci-dev (10)
- # biff (5)
- # calva (9)
- # cherry (1)
- # cider (44)
- # clj-kondo (31)
- # cljfx (1)
- # clojure (108)
- # clojure-europe (32)
- # clojure-norway (12)
- # clojurescript (15)
- # conjure (3)
- # cursive (8)
- # datahike (1)
- # datalevin (19)
- # datascript (1)
- # datomic (59)
- # emacs (4)
- # graphql (3)
- # jobs (1)
- # luminus (6)
- # meander (9)
- # membrane (45)
- # nbb (67)
- # off-topic (16)
- # portal (3)
- # remote-jobs (1)
- # scittle (8)
- # shadow-cljs (46)
- # test-check (7)
- # tools-deps (5)
- # vim (63)
- # web-security (11)
- # xtdb (15)
It's been a little longer than I expected, but I'm using some of my 20% time at Cognitect to work on issues and PRs in lacinia. It's good to be back.
2

👍 6
❤️ 2
I'm looking at https://github.com/walmartlabs/lacinia-pedestal/issues/112 and I'm throwing the floor open about what the lacinia-pedestal behavior should be when an operation times out. My initial take is that the lacinia-pedestal handler should throw an exception so that an application-specific interceptor can handle the exception - that interceptor could log the exception and decide what kind of response to send to the client.