You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
when I run annotate_data, I encounter the following error: "libgomp: Thread creation failed: Resource temporarily unavailable, Thread creation failed: Resource temporarily unavailable". Is this caused by insufficient server resources or an issue with the libgomp package? If it is due to insufficient resources, how can I check how many resources this function requires? Thank you.
Hi, this is caused by block on server side. We released popV 0.5 with improved API and training/inference speed (tested for up to 3 million cells and more critical 300 reference batches). If the issue still arises there and the thread management in underlying tools is not good by us, please reopen. Please try to copy the full error message as it helps to debug these things.
Report
Hello,
when I run annotate_data, I encounter the following error: "libgomp: Thread creation failed: Resource temporarily unavailable, Thread creation failed: Resource temporarily unavailable". Is this caused by insufficient server resources or an issue with the libgomp package? If it is due to insufficient resources, how can I check how many resources this function requires? Thank you.
Version information
_libgcc_mutex 0.1
importlib-resources 6.5.2
jaxlib 0.4.38
joblib 1.4.2
libclang 18.1.1
libffi 3.4.2
libgcc 14.2.0
libgcc-ng 14.2.0
libgomp 14.2.0
liblzma 5.6.3
libnsl 2.0.1
libsqlite 3.47.2
libstdcxx 14.2.0
libuuid 2.38.1
libxcrypt 4.4.36
libzlib 1.3.1
matplotlib 3.10.0
stdlib-list 0.11.0
urllib3 2.3.0
nvidia-cuda-cupti-cu12 12.4.127
nvidia-cuda-nvrtc-cu12 12.4.127
nvidia-cuda-runtime-cu12 12.4.127
safetensors 0.5.2
tensorboard 2.18.0
tensorboard-data-server 0.7.2
tensorflow 2.18.0
tensorflow-io-gcs-filesystem 0.37.1
tensorstore 0.1.71
python 3.10.16
python-annoy 1.17.3
python-dateutil 2.9.0.post0
python_abi 3.10
The text was updated successfully, but these errors were encountered: