It is possible for stderr output to be swallowed unexpectadly
Expected behavior
All stderr is handled. By defaut it is printed to the repl buffer.
Actual behavior
In some cases, a stderr output can be lost.
Steps to reproduce the problem
bb process logs the process err to stdout, but it never shows.
mkdir example-stderr-gone
cd example-stderr-gone
bb print-deps > deps.edn
cat <<EOF > foo.clj
(ns foo
(:require
[babashka.process :as process]))
(process/shell "ls" "nothing")
EOF
(find-file "foo.clj")
(cider-jack-in-clj)
(cider-eval-buffer)
Environment & Version information
CIDER version information
CIDER 1.8.0-snapshot (package: 1.8.0-snapshot), nREPL 1.0.0 Clojure 1.11.1, Java 11.0.16
JDK distribution
openjdk version "11.0.16" 2022-07-19 LTS OpenJDK Runtime Environment Corretto-11.0.16.8.1 (build 11.0.16+8-LTS) OpenJDK 64-Bit Server VM Corretto-11.0.16.8.1 (build 11.0.16+8-LTS, mixed mode)
I think the issue is on the nrepl-client or nrepl layer of things. Because when I type that into the repl buffer, I also don't get the warning.
Did you check the *nrepl-server* buffer? (if you used cider-jack-in) Sometimes output ends up in it.
yes it shows in the nrepl-server buffer - which does make this issue less urgent. For my taste it would be enough to know about this and check the nrepl-buffer. But I think as a user you might be confused and don't know.