You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using --quiet only error logs should be displayed.
But when using a JShell script two logs are still emitted when launching JBang from Docker:
Aug 16, 2024 12:25:34 PM java.util.prefs.FileSystemPreferences$1 run
NFO: Created user preferences directory.
To Reproduce
Create this script in a test.jsh file:
System.out.println("Hello World!");
Launch it via Docker with --quiet:
docker run -v `pwd`:/ws --workdir=/ws -ti jbangdev/jbang-action --quiet test.jsh
Expected behavior
No INFO logs should be displayed when running with --quiet in Docker.
This is actually not JBang giving that message, but it's the JVM itself.
But I'm guessing that the message will always appear on any invocation of a the action so we should probably prevent it from displaying.
The easiest way would be to simply create that folder inside the docker image when the action gets built.
Another option would be to suppress JVM info messages, but I feel that's not something that JBang should be doing (some users might actually want those messages).
Describe the bug
When using
--quiet
only error logs should be displayed.But when using a JShell script two logs are still emitted when launching JBang from Docker:
To Reproduce
Create this script in a
test.jsh
file:Launch it via Docker with
--quiet
:Expected behavior
No INFO logs should be displayed when running with
--quiet
in Docker.JBang version
The text was updated successfully, but these errors were encountered: