Ignore multiple calls to set_runner_ray with kwarg noop_if_initialized #728
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.
set_runner_ray(...)
more than once per process, they will incur a RuntimeError. The intention here is to be very explicit that this behavior is not encouraged, as setting the runner more than once can potentially corrupt the state of Daft's caching.noop_if_initialized
. If set toTrue
, subsequent calls toset_runner_ray
are ignored and have no effect. We log a warning when this happens.