Random error on `.explode()`
See original GitHub issueSystem information
- OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 21.04
- Modin version (
modin.__version__
): 0.10.2 - Python version: 3.7
- Code we can use to reproduce:
import modin.pandas as pd
# create a bunch of pd.DataFrame-s
df = df.explode([_bunch of col names_])
Describe the problem
Random error, works again once all the cells in Jupyter are ran again (without any modifications):
UserWarning: `DataFrame.explode` defaulting to pandas implementation.
---------------------------------------------------------------------------
Exception Traceback (most recent call last)
<timed exec> in <module>
~/anaconda3/envs/venv_ray/lib/python3.7/site-packages/modin/pandas/dataframe.py in explode(self, column, ignore_index)
817 """
818 return self._default_to_pandas(
--> 819 pandas.DataFrame.explode, column, ignore_index=ignore_index
820 )
821
~/anaconda3/envs/venv_ray/lib/python3.7/site-packages/modin/pandas/base.py in _default_to_pandas(self, op, *args, **kwargs)
455 args = try_cast_to_pandas(args)
456 kwargs = try_cast_to_pandas(kwargs)
--> 457 pandas_obj = self._to_pandas()
458 if callable(op):
459 result = op(pandas_obj, *args, **kwargs)
~/anaconda3/envs/venv_ray/lib/python3.7/site-packages/modin/pandas/dataframe.py in _to_pandas(self)
2848 pandas.DataFrame
2849 """
-> 2850 return self._query_compiler.to_pandas()
2851
2852 def _validate_eval_query(self, expr, **kwargs):
~/anaconda3/envs/venv_ray/lib/python3.7/site-packages/modin/backends/pandas/query_compiler.py in to_pandas(self)
253
254 def to_pandas(self):
--> 255 return self._modin_frame.to_pandas()
256
257 @classmethod
~/anaconda3/envs/venv_ray/lib/python3.7/site-packages/modin/engines/base/frame/data.py in to_pandas(self)
2232 ErrorMessage.catch_bugs_and_request_email(
2233 not df.axes[axis].equals(self.axes[axis]),
-> 2234 f"Internal and external indices on axis {axis} do not match.",
2235 )
2236 df.index = self.index
~/anaconda3/envs/venv_ray/lib/python3.7/site-packages/modin/error_message.py in catch_bugs_and_request_email(cls, failure_condition, extra_log)
61 "Internal Error. "
62 "Please email bug_reports@modin.org with the traceback and command that"
---> 63 " caused this error.\n{}".format(extra_log)
64 )
65
Exception: Internal Error. Please email bug_reports@modin.org with the traceback and command that caused this error.
Internal and external indices on axis 1 do not match.
Source code / logs
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
How can explode elements randomly? - php - Stack Overflow
How can explode elements randomly? · 1. shuffle($array) then array_pop($array) for each random element you want. – Alex Howansky. Jan 25, 2018 at ......
Read more >Explode then select 3 random arrays - PHPBuilder Forums
We might need some clarification, as explode() only creates 1 array. Are you perhaps asking how to select 3 random elements from that...
Read more >explode - Manual - PHP
Returns an array of strings created by splitting the string parameter on boundaries formed by the separator . If separator is an empty...
Read more >Issue with loss exploding after a random number of epochs
Hello everybody, I have a problem in training a network composed of both convolutional and recurrent layers. Specifically, the training goes ...
Read more >The Grand C++ Error Explosion Competition on Tumblr
You check out the code and open a random file in an editor. It appears on the screen. After just one microsecond of...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Haha, sounds good. The elusive bugs are always the most fun to work on. Please let us know if it happens again!
Will do. Thanks for the quick support! Couldn’t reproduce on ray 1.7.0.