Resolve the iterator outside of the hub context to not mess with the state of the RNG #23
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.
Hi. We're making use of this pytest fixture:
We also make use of https://pypi.org/project/pytest-snapshot/. And when
pytest-sentry
is installed, it breaks our tests because somehow the RNG state gets modified.This PR fixes our problem and I'm wondering if it's also an acceptable default for everyone.
If not, could we have a way to configure pytest-sentry so that we don't have to use a fork?