This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-09-07
Channels
- # architecture (35)
- # babashka (9)
- # beginners (31)
- # biff (15)
- # calva (8)
- # cider (7)
- # clerk (4)
- # clj-kondo (24)
- # clj-yaml (10)
- # clojure (58)
- # clojure-europe (65)
- # clojure-japan (1)
- # clojure-nl (1)
- # clojure-norway (89)
- # clojure-spec (1)
- # clojure-sweden (1)
- # clojure-uk (8)
- # clojurescript (14)
- # cursive (3)
- # datahike (1)
- # datomic (29)
- # emacs (8)
- # graalvm (20)
- # graphql (1)
- # gratitude (2)
- # helix (6)
- # hyperfiddle (65)
- # jobs-discuss (7)
- # leiningen (1)
- # life (3)
- # lsp (6)
- # malli (14)
- # missionary (12)
- # nrepl (8)
- # off-topic (24)
- # polylith (29)
- # reagent (14)
- # sci (14)
- # shadow-cljs (6)
- # spacemacs (10)
- # sql (4)
How can I enable operation logging in nrepl server? Our clojure application is hosted on an AWS EC2 instance, that multiple user connect via ssh. As it's a production machine, we want access to the repl and operations executed on it to be logged.
Taking a quick look at the nrepl codebase, it doesn't appear to have logging. Which is a sensible choice, because it shouldn't conflict with users' dependency trees or choices of logging framework. It's probably reasonably easy to add your own middleware to your application's nrepl stack. That piece of middleware would log e.g. incoming and outcoming messages. Be mindful of passwords or huge data - anything you would not want to log.
Yeah, there's no built-in logging. We discussed this in the past and some prototyping work was done, but nothing more https://github.com/nrepl/nrepl/issues/85
Thanks for the response @U45T93RA6 and @U051BLM8F Middleware makes sense. Also, we want to log just the requests for now, so the size of the log is not an issue. Thanks for the heads up though. 😃
Hey folks, I'm using a TTY nREPL server, when I connect remotely I can't send a CTRL+C or CRTL+D to exit the nREPL connection, is there any way to do it?
those commands are not really things that are transmitted over the wire from client to server, depending on how you terminal is setup client may not even get ctrl+d, it may just get the end of stream signal when reading from stdin
so I would start by looking at the clients you are using (nc, telnet) and the terminal you are using them in
with nc and telnet I can't close my session sending these signals, is there any reason for this?