I enabled the data-loader in freva-dev an noticed that the loading failed the code rest-api (not the data-loader) wanted to import xarray and all the backends. This was because I added the cloudpickle dataset object to the cache.
This cached dataset is used internally by the data-loader code, not by the rest-api. Simple solution: add the xarray dataset to a dedicated cache entry. The problem should be solved.
What bothers me a little bit is that the tests couldn't fetch this as the code is running in the same python environment and hence all libraries are available. But I guess we'll have to live with that.
I enabled the data-loader in freva-dev an noticed that the loading failed the code rest-api (not the data-loader) wanted to import xarray and all the backends. This was because I added the cloudpickle dataset object to the cache.
This cached dataset is used internally by the data-loader code, not by the rest-api. Simple solution: add the xarray dataset to a dedicated cache entry. The problem should be solved.
What bothers me a little bit is that the tests couldn't fetch this as the code is running in the same python environment and hence all libraries are available. But I guess we'll have to live with that.