Sylvain

Hi @p1c2u , Yes I did this, I actually realise I forgot to show the python code: ```python from openapi_spec_validator import validate_spec, factories from openapi_core import create_spec from openapi_core.shortcuts import...

I tried ```$ref: 'test.json'``` and ```$ref: './test.json'``` both return the same error as explained above. The latter works better in some other packages. Actually the problem is not in finding...

@p1c2u what do you mean fixing `null issue?

so you changed to ``` // test.json { "$schema": "http://json-schema.org/draft-04/schema#", "title": "Test", "type": ["string"], "format": "date-time" } ``` is that correct? cause for me I still get the very same...

Ok, but then it is not anymore a json-schema but a openapi. So it is not possible to mix them together in that case.

ok, so after hours of research it's actually possible folowing: [this](https://philsturgeon.uk/api/2018/03/30/openapi-and-json-schema-divergence/) and [this](https://philsturgeon.uk/api/2018/04/13/openapi-and-json-schema-divergence-solved/). So, using a json-schema file, passing it through the json-schema-to-openapi converter and then in the openapi-validator. The...

@quasiben @fjetter thank you for your answers. so this is indeed a bug it seems. Should I use another API in order to get the resources from inside the worker?

Thanks for your answer @quasiben . So I tried with what you propose, and the exact same issue arises. As soon as I use publish_dataset, then ```available_resources == total_resources```. Otherwise...

But then this is still an issue and for us that means we cannot upgrade dask anymore since we do run computations in the background.

@fjetter , @quasiben : sorry to insist here but is there any news/plan on this issue?