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
information messages such as "Another process has locked" and "lock acquired" should be printed on stderr, not stdout, as they aren't really part of the output of a command.
An example where we caught the problem
opam switch set-invariant --packages=ahrefs-setup,ahrefs-dev-tools-deps,ocaml-base-compiler.$(opam show ocaml-base-compiler --field=installed-version),ahrefs-all-deps
Can end up being executed as
opam switch set-invariant --packages=ahrefs-setup,ahrefs-dev-tools-deps,ocaml-base-compiler.Another process has locked /home/user/monorepo/.opam/repo/state-11ABC690.cache, waiting (C-c to abort)... lock acquired. 4.14.0,ahrefs-all-deps
This is true for lock messages but probably also applied to other informational messages.
The text was updated successfully, but these errors were encountered:
Yes, for example, if the internal repository data cache (marshalled data) isn't up-to-date or has been removed, opam will try to save that file by default
information messages such as "Another process has locked" and "lock acquired" should be printed on stderr, not stdout, as they aren't really part of the output of a command.
An example where we caught the problem
Can end up being executed as
This is true for lock messages but probably also applied to other informational messages.
The text was updated successfully, but these errors were encountered: