Open Lukas113 opened 8 months ago
A minor update: I set the xarray-constraint on the Feedstock because it's an issue from ska-sdp-func-python and not Karabo. In addition, I removed the build-nr fixings to enable constaint-updates. Otherwise, each legacy karabo installation would be corrupt if a feedstock-wheel needs an update.
The hotfix is finished, as soon as there is an updated build of ska-sdp-func-python available with a larger build-nr. However, I'll try to create a reproducible test-case to catch this error.
For the imaging part of Karabo while running
source_detection.ipynb
, I've encountered the following error withxarray
2023.11 (see traceback). When I downgradedxarray
to 2023.2 (release before blame commit to raise ValueError), there was no such error and everything worked fine. Because this error is caused throughRASCIL
andska_sdp_func_python
(see traceback), I think fixing this error is out of my control. If my assessment is correct, when should fix it as follows:First, just constrain
xarray
to be <= 2023.2. However, this also constrainspandas
to be < 2 (conda-resolver said so). And because these two libraries are widely used libraries, we should address this issue further. However, this might require some effort. Firstly, becauseRASCIL
hasn't contrainedska_sdp_func_python
&ska_sdp_func
versions, I'm concerned that the latest release ofRASCIL
1.1.0 (April 2023) might not be compatible with the (hopefully fixed) major release of ska-sdp-func 1.0 (November 2023). In addition, we also need to build the according conda-wheels after testing.Long story short: As a hotfix, I'll constrain
xarray
<= 2023.2 (and accept thepandas
downgrade for the moment). The best-case scenario would be thatRASCIL
soon does a new release, where we could fix the accordingska-sdp
deps. I don't think that building a dirty conda-wheel (10 months after the last release) ofRASCIL
is a good solution. If there's a better suggestion, I'd like to hear it.