Only 4 jobs run, while a repo had 9 commits
see discussion at https://huggingface.slack.com/archives/C3XM337MW/p1662737235920349?thread_ts=1662735709.930169&cid=C3XM337MW

The `splits_reponses` and `first_rows_responses` queues only contain 4 jobs:

  <img width="444" alt="Capture d’écran 2022-09-09 à 17 51 52" src="https://user-images.githubusercontent.com/1676121/189391009-cb8f0fce-6c55-4ff6-8fe6-fad759150992.png">

The four jobs are successful for the splits, whereas two of them are erroneous for the first rows. The last job has been run manually by me, not by the webhook.

At the same time, the commit history is the following (9 commits): https://huggingface.co/datasets/davanstrien/encyclopedia_britannica/commits/main

<img width="582" alt="Capture d’écran 2022-09-09 à 17 53 47" src="https://user-images.githubusercontent.com/1676121/189391392-d8425287-242a-4bc6-be41-834b6bb682ba.png">

This might be due to some of the following hypotheses:
- some webhooks have not been sent after a commit on the dataset repo
  - low probability: why?
- the webhooks have not been received by the API
  - low probability: why?
- the API did not add the job
  - low probability: why?
- the job already existed in the "WAITING" status, so the webhook was ignored
  - low probability because the last run job should have been successful 
- something else

We lack information to investigate:
- the ["webhook: refresh dataset xxx"](https://github.com/huggingface/datasets-server/blob/833ea70034a73274d2cec7b4425fe2f8b9d32e53/services/api/src/api/routes/webhook.py#L54) logs are in "debug" level, and they are not in [kibana](https://kibana.elastic.huggingface.tech/app/discover#/?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-30m,to:now))&_a=(columns:!(),filters:!(),index:'24d42510-a44e-11ec-bb45-ad141ad1c5f8',interval:auto,query:(language:kuery,query:'kubernetes.container.name:%20%22datasets-server-api%22%20and%20%20message:%20%22webhook%22'),sort:!(!('@timestamp',desc))))
- the database does not contain the git version of the repository (we could add it to the jobs -> all the jobs, and to the cache -> only the latest)
Only 4 jobs run, while a repo had 9 commits: see discussion at https://huggingface.slack.com/archives/C3XM337MW/p1662737235920349?thread_ts=1662735709.930169&cid=C3XM337MW

The `splits_reponses` and `first_rows_responses` queues only contain 4 jobs:

  <img width="444" alt="Capture d’écran 2022-09-09 à 17 51 52" src="https://user-images.githubusercontent.com/1676121/189391009-cb8f0fce-6c55-4ff6-8fe6-fad759150992.png">

The four jobs are successful for the splits, whereas two of them are erroneous for the first rows. The last job has been run manually by me, not by the webhook.

At the same time, the commit history is the following (9 commits): https://huggingface.co/datasets/davanstrien/encyclopedia_britannica/commits/main

<img width="582" alt="Capture d’écran 2022-09-09 à 17 53 47" src="https://user-images.githubusercontent.com/1676121/189391392-d8425287-242a-4bc6-be41-834b6bb682ba.png">

This might be due to some of the following hypotheses:
- some webhooks have not been sent after a commit on the dataset repo
  - low probability: why?
- the webhooks have not been received by the API
  - low probability: why?
- the API did not add the job
  - low probability: why?
- the job already existed in the "WAITING" status, so the webhook was ignored
  - low probability because the last run job should have been successful 
- something else

We lack information to investigate:
- the ["webhook: refresh dataset xxx"](https://github.com/huggingface/datasets-server/blob/833ea70034a73274d2cec7b4425fe2f8b9d32e53/services/api/src/api/routes/webhook.py#L54) logs are in "debug" level, and they are not in [kibana](https://kibana.elastic.huggingface.tech/app/discover#/?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-30m,to:now))&_a=(columns:!(),filters:!(),index:'24d42510-a44e-11ec-bb45-ad141ad1c5f8',interval:auto,query:(language:kuery,query:'kubernetes.container.name:%20%22datasets-server-api%22%20and%20%20message:%20%22webhook%22'),sort:!(!('@timestamp',desc))))
- the database does not contain the git version of the repository (we could add it to the jobs -> all the jobs, and to the cache -> only the latest)