Cache entries seem to be deleted again and again if dataset page is accessed when the jobs are running
I observed on https://huggingface.co/datasets/wisenut-nlp-team/FiD-Merge-Dataset_temp_addlong:

- erroneous contents: https://huggingface.co/datasets/wisenut-nlp-team/FiD-Merge-Dataset_temp_addlong/discussions/2
- I recreated the dataset through the admin UI
- some cache entries were created, the config-parquet-and-info job was still pending
- I accessed the dataset page
- then, the dataset status only showed no cache entries, and a pending job for dataset-config-names

It means that accessing one of the API endpoints triggered an update of the dataset (delete everything, and recreate it from the start).

It's an awful bug, related to https://github.com/huggingface/datasets-server/pull/2244. I'm on it.
Cache entries seem to be deleted again and again if dataset page is accessed when the jobs are running: I observed on https://huggingface.co/datasets/wisenut-nlp-team/FiD-Merge-Dataset_temp_addlong:

- erroneous contents: https://huggingface.co/datasets/wisenut-nlp-team/FiD-Merge-Dataset_temp_addlong/discussions/2
- I recreated the dataset through the admin UI
- some cache entries were created, the config-parquet-and-info job was still pending
- I accessed the dataset page
- then, the dataset status only showed no cache entries, and a pending job for dataset-config-names

It means that accessing one of the API endpoints triggered an update of the dataset (delete everything, and recreate it from the start).

It's an awful bug, related to https://github.com/huggingface/datasets-server/pull/2244. I'm on it.