Set the Bundler UI level to silent to prevent output to stdout #1199
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Fixes #1723
If users have Bundler's logging level configured to
info
ordebug
, internals will print to stdout and mess up the client/server communication. This happens when invoking methods likeBundler.locked_gems
orspecs
. Here's an example.We use these methods in two places
Implementation
Set the Bundler UI level to
silent
so that it does not print anything regardless of user configurations. One of them will go away once we move tobundler-compose
and just the one ininternal
will remain.