Failing CI (possibly related to ngio 0.2.4->0.2.8 update)

[tcompa]

The CI in #949 is failing, e.g. with this error:

         # Validate plate zarr attributes:
        plate_attrs = zarr.open_group(plate_zarr).attrs.asdict()
>       assert plate_attrs == expected_MIP_plate_attrs
E       AssertionError: assert {'plate': {'a...: 'B'}], ...}} == {'plate': {'a...: '0.4', ...}}
E         Differing items:
E         {'plate': {'acquisitions': [{'id': 0, 'name': '20200812-CardiomyocyteDifferentiation14-Cycle1'}], 'columns': [{'name': '03'}], 'name': 'plate_mip.zarr', 'rows': [{'name': 'B'}], ...}} != {'plate': {'acquisitions': [{'id': 0, 'name': '20200812-CardiomyocyteDifferentiation14-Cycle1'}], 'columns': [{'name': '03'}], 'rows': [{'name': 'B'}], 'version': '0.4', ...}}
E         Full diff:
E           {
E            'plate': {'acquisitions': [{'id': 0,
E                                        'name': '20200812-CardiomyocyteDifferentiation14-Cycle1'}],
E                      'columns': [{'name': '03'}],
E         +            'name': 'plate_mip.zarr',
E                      'rows': [{'name': 'B'}],
E                      'version': '0.4',
E                      'wells': [{'columnIndex': 0,
E                                 'path': 'B/03',
E                                 'rowIndex': 0}]},
E           }

Note that this PR includes the

  - Updating ngio (0.2.4 -> 0.2.8)

update.

@lorenzocerrone do you know whether this is some breaking change that took place in recent ngio versions? If so, we should either fix it or pin the ngio version, because installing fractal-tasks-core today wold lead to a broken version.

[lorenzocerrone]

It's possible, I am looking into it. There should be no breaking changes, but I fix a minor bug when writing the plate metadata.

[lorenzocerrone]

CIs are passing now. There were two minor changes that did not affect task logic, but they failed in testing.

@tcompa should we update the pin on ngio? fractal-task-core will work with all version ngio>=0.2.4 but tests will pass only for ngio>=0.2.5

[tcompa]

should we update the pin on ngio? fractal-task-core will work with all version ngio>=0.2.4 but tests will pass only for ngio>=0.2.5

The CI won't run with any old version of ngio, then let's do what makes life easier for other packages. Since I guess that some packages still depend on fractal-tasks-core and ngio, I guess the easiest is to allow ngio=0.2.4 as well.

[jluethi]

+1 on being as wide in the fractal-tasks-core ngio dependency as we can be, as long as people rely on both dependencies => having ngio>=0.2.4 sounds good