Deployed.

Trying to bisect the issue and failed (multiple dimensions got the best of me, master ok, debian build in stable ko... i need to improve my tooling there).

So, the debian/unstable broke which is fixed now [1] (it wasd missing one new deps to
test the migration part).

Landed. Remains to deploy. I'll attend to that tomorrow.

Pushed and tag swh.web.client v0.3.0 with the new endpoint ^
(ideally we could want at least 2 other endpoints, one to check the status
on one save code now request, another to possibly list in a paginated way
the status of the save code now, a-la ui to be symmetric with that new
endpoint, tasks to open ;)

Nevertheless, that error should have been detected on the first loading so some adaptation is needed in the svn loader.

In any case, independently from this, for the monitoring, I was set on modifying the
actual svn origin used to something else not hosted on github.

lgtm

Thanks, this is quite useful indeed.

So the cli opened in D5559 has now been rewritten slightly (the diff is now fully tested though). See the diff for details.

Browsing though the save code now ui with increment of 100 per page.

Rescheduled the ones not yet scheduled.
As expected, some worked, some failed but tl; dr the status are updated...
No more not yet scheduled... But...

ok so the 'not created' ones are apparently failing origins so the issue is about the report
of the state which is somehow wong. [1] There is a task for that (or something near
enough) [2]

Most probably yes.

Thanks for looking into this. If I look at https://grafana.softwareheritage.org/d/WXRVVc_Mz/save-code-now?viewPanel=4&orgId=1&from=1617954242247&to=1617975842247&var-environment=production&var-instance=moma.internal.softwareheritage.org&var-status=All&var-load_task_status=All&var-visit_type=All it seems there are also some 255 requests "not yet scheduled". Maybe it's the same issue?

With [1], the following has been rescheduled [2]

We could reschedule the origins through:
psql ... | xargs swh scheduler task respawn {} \;

It'd be best if we distinguish directly from the listing view such details.

Thanks for the heads up ;)

The error is related to that github origin erroneously submitted with a svn visit type.