Looks like swh.deposit v0.0.74 has been deployed, but it generates tasks according to T2024 which is still WIP.

see task arguments of recent tasks like:

Task 217689078
  Next run: il y a 2 jours (2019-10-28 09:44:51+00:00)
  Interval: 1 day, 0:00:00
  Type: load-deposit
  Policy: oneshot
  Status: next_run_scheduled
  Priority: 
  Args:
  Keyword args:
    deposit_id: 336
    url: 'https://hal.archives-ouvertes.fr/hal-02132469'

vs.

Task 215063600
  Next run: il y a un mois (2019-09-20 13:24:34+00:00)
  Interval: 1 day, 0:00:00
  Type: load-deposit
  Policy: oneshot
  Status: completed
  Priority: 
  Args:
  Keyword args:
    archive_url: '/1/private/hal/333/raw/'
    deposit_meta_url: '/1/private/hal/333/meta/'
    deposit_update_url: '/1/private/hal/333/update/'

So as far as I understand it, we should revert deposit back to 0.0.73 and recreate these tasks with proper arguments.

I've created 'old-style' tasks, using swh scheduler

$ swh scheduler task add load-deposit -p oneshot  -P high \
    archive_url=/1/private/hal/336/raw/ \
    deposit_meta_url=/1/private/hal/336/meta/ \
    deposit_update_url=/1/private/hal/336/update/ 

@olasd can you (if it's not too much painful) revert python3-swh.deposit to 0.0.73?

In T2051#38043, @douardda wrote:

@olasd can you (if it's not too much painful) revert python3-swh.deposit to 0.0.73?

We don't really archive old Debian package versions, so it's not exactly convenient (plus using "not the last version" breaks some assumptions on deployments).

It'd be much easier to revert rDDEP12e3966b168e7be7b19aeb8c0a8d664667c81b3d and reintroduce it when the loader is ready to accept it.

what's the current status of this task?

A full deposit from HAL doesn't work.
It seems to be on HAL side, the deposits stay in partial status and aren't digested.
On HAL interface after moderation there is "Application Error".
I signalled this to Bruno and he said he's fixing it.