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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FIX-#4564: Workaround import issues in Ray: auto-import pandas on python start if env var is set #4603
FIX-#4564: Workaround import issues in Ray: auto-import pandas on python start if env var is set #4603
Changes from all commits
e2fe3c5
cddfba1
a8d568d
848d8b2
843dbbb
965c5b9
2eb728f
158f0f3
2373716
23bdcec
e426ce0
a24c723
0ac7c82
995febd
49029e2
2a8b4f7
887a5f4
01682b0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you check this case? I can't find that extra parameters could be provided in case of existing cluster https://github.com/ray-project/ray/blob/master/python/ray/_private/worker.py#L1400-L1412
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I hadn't, but apparently extra ones would just get ignored, and, if in the future we'll add more arguments than
runtime_env
it would be useful.As for the runtime environment being different, there is a code later on checking the variables. It should give a warning to the user.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you elaborate why it would be useful?
What the code do you mean?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This creates one central place to add more arguments to
ray.init()
instead of copy-pasting them in several different places.modin/modin/core/execution/ray/common/utils.py
Lines 170 to 177 in e426ce0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't hit this branch in case of cluster init.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huh?.. we either call
ray.init()
or hit thiselse:
branch.We hit
ray.init()
at line 84 (underif cluster:
) or at line 158 (inelse
branch of thatif cluster
).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was just wondering if we should check the runtime environment after ray.init() in case Modin itself initializes Ray? Because of this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good point!