Update probe import path

[hkjeldsberg]

No description provided.

[johannesring]

@hkjeldsberg - I see you have the same problems with CI as we had in VaSP. The fix for us was to downgrade the expat Conda package to 2.5.0.

[jorgensd]

@hkjeldsberg - I see you have the same problems with CI as we had in VaSP. The fix for us was to downgrade the expat Conda package to 2.5.0.

Maybe we could ask @minrk to have a look and see if he can se what is going wrong?
If you know what package/function that relies on expat.

[johannesring]

It is vtk that depens on expat. There are some more info here and here.

[hkjeldsberg]

Interesting. Will have to pin expat until they release a fix. @johannesring thanks a bunch for pointing this out.

[minrk]

From https://gitlab.kitware.com/vtk/vtk/-/issues/19258 it looks like conda-forge should pin libexpat 2.5 in vtk.

Done in conda-forge/vtk-feedstock#321 and conda-forge/conda-forge-repodata-patches-feedstock#682 . Once those land, conda-forge packages should install libexpat 2.5 with vtk instead of 2.6, but for now you should be able to apply the pin yourself.