This repository was archived by the owner on Nov 30, 2024. It is now read-only.
Fix with_isolated_stderr
so it does not leak.
#68
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.
Without ensure, it leaves $stderr set to a different value.
Fixes rspec/rspec-core#1534.
So that rspec-core issue wasn't actually a problem with rspec-core; it was a problem with this line in an rspec-mocks test:
https://github.com/rspec/rspec-mocks/blob/83c1456d9e9bddcb624b00f636340a837f42e6b2/spec/rspec/mocks/argument_matchers_spec.rb#L209
...which used
with_isolated_stderr
, was wrapping a spot where an exception was raised, and as a result$stderr
would remain silenced after that. That in turn cased the exception in the formatter not to be printed to the console like it normally would be./cc @JonRowe