Open sharmuz opened 2 months ago
Hi @sharmuz,
Thank you for reporting this, the culprit is probably lightgbm
or xbgboost
. We'll try to investigate this issue asap.
Hi @sharmuz, are you running on a Mac with an M chip? If so, some of the dependencies installed with PyPI might not use the correct dependencies for the M-chip (e.g. they install the intel version). For me this is fixed when installing the following dependencies with conda before installing darts:
conda install catboost pytorch lightgbm -y
pip install darts
@dennisbader I'm on a 2020 Intel Mac.
Also I'm using uv for package management. I could try having it install lightgbm from source using gcc. This is the option FYI
@sharmuz, a little bit of follow-up; did the no-binary-package
option of uv for darts dependencies solved the issue?
@madtoinou thanks for the nudge - I gave it a go, but lightgbm is failing to build using gcc. I created a new issue:
Describe the bug When
darts.models.forecasting.croston
is run it importsstatsforecast.core
, within whichthreadpoolctl.ThreadpoolController()
is created. This then detects that both Intel libiomp and LLVM libomp are both loaded. This throws a warning due to the issue outlined here."Therefore this problem would only happen if some packagers decide to start shipping Python packages built with LLVM/Clang instead of GCC"
Note that if
statsforecast.core
is imported outside of darts, no such warning is thrown. So it seems that a dependency of darts is built with LLVM. Any idea what's at fault?To Reproduce
import darts.models.forecasting.croston
Expected behavior No warning.
System (please complete the following information):
Additional context Add any other context about the problem here.