-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[C++] Fatal error condition occurred in aws_thread_launch #20039
Comments
Antoine Pitrou / @pitrou: |
Antoine Pitrou / @pitrou: |
F. H.: |
H. Vetinari: |
Hi, I am getting randomly the following error when first running inference with a Tensorflow model and then writing the result to a
.parquet
file:My colleague ran into the same issue on Centos 8 while running the same job + same environment on SLURM, so I guess it could be some issue with tensorflow + pyarrow.
Also I found a github issue with multiple people running into the same issue:
huggingface/datasets#3310
It would be very important to my lab that this bug gets resolved, as we cannot work with parquet any more. Unfortunately, we do not have the knowledge to fix it.
Environment: -
uname -a
:Linux datalab2 5.4.0-91-generic #102-Ubuntu SMP Fri Nov 5 16:31:28 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
mamba list | grep -i "pyarrow\|tensorflow\|^python"
pyarrow 6.0.0 py39hff6fa39_1_cpu conda-forge
python 3.9.7 hb7a2778_3_cpython conda-forge
python-dateutil 2.8.2 pyhd8ed1ab_0 conda-forge
python-flatbuffers 1.12 pyhd8ed1ab_1 conda-forge
python-irodsclient 1.0.0 pyhd8ed1ab_0 conda-forge
python-rocksdb 0.7.0 py39h7fcd5f3_4 conda-forge
python_abi 3.9 2_cp39 conda-forge
tensorflow 2.6.2 cuda112py39h9333c2f_0 conda-forge
tensorflow-base 2.6.2 cuda112py39h7de589b_0 conda-forge
tensorflow-estimator 2.6.2 cuda112py39h9333c2f_0 conda-forge
tensorflow-gpu 2.6.2 cuda112py39h0bbbad9_0 conda-forge
Reporter: F. H.
Assignee: Uwe Korn / @xhochy
Related issues:
Externally tracked issue: huggingface/datasets#3310
Note: This issue was originally created as ARROW-15141. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: