Open vijaye12 opened 1 month ago
@vijaye12 please include the output of pip freeze
for a known working state in colab.
If we want to honor google-colab 1.0.0 requires pandas==2.0.3
and similar constraints it might require a separate release or branch/tagging strategy per platform as other platforms might bring in their own constraints.
Documenting here, from internal discussions.
Currently, some operations we do are not compatible with pandas==2.0.3
. However, if you pip install as follows, the pyarrow and requests issues are resolved:
!pip install git+https://github.com/IBM-granite/granite-tsfm.git "datasets<2.20"
Tagging this with help wanted. Tests are currently failing for a downgraded version of pandas. There have been numerous changes in the pandas 2.x series of releases -- looking for someone to help identify fixes for these issues. I believe there are issues with options supported by group-by (and the default behavior) as well as how pandas defines frequency / period specifiers for daterange.
@wgifford I'll see if I can make any headway tomorrow.
While running the TTM colab notebook, we get the following error. Seems some library in public tsfm needs upgrade. After upgrading pandas and pyarrow to the latest version in the notebook, the error is resolved..
cudf-cu12 24.4.1 requires pandas<2.2.2dev0,>=2.0, but you have pandas 2.2.2 which is incompatible. cudf-cu12 24.4.1 requires pyarrow<15.0.0a0,>=14.0.1, but you have pyarrow 16.1.0 which is incompatible. google-colab 1.0.0 requires pandas==2.0.3, but you have pandas 2.2.2 which is incompatible. google-colab 1.0.0 requires requests==2.31.0, but you have requests 2.32.3 which is incompatible. ibis-framework 8.0.0 requires pyarrow<16,>=2, but you have pyarrow 16.1.0 which is incompatible.