Page MenuHomeSoftware Heritage

"Save code now" seems to be stuck
Closed, ResolvedPublic

Description

"Save code now" seems to hang. In my "Save code now" dashboard all requests since yesterday 20:00 appear as "not yet scheduled". According to the status page ("Save Code Now requests in queue") there is only one request in the queue and the service seems to work correctly. However, for my understanding, there are currently 30 requests in the queue (requests with the status "not yet scheduled). See screenshot


If the service is working correctly, it would be good to see some more information about the status ( like "Request xyz in process", time remaining, ...).

Event Timeline

mwagner created this object in space S1 Public.
zack triaged this task as High priority.Mon, Jun 7, 9:44 AM
zack added a project: Save Code Now.

Thanks for the bump! It was stuck and not it got unstuck.

If the service is working correctly, it would be good to see some more information about the status ( like "Request xyz in process", time remaining, ...).

That's a good idea.
Although, we cannot really compute an eta, it really depends
on the repositories size which we don't really know in advance.

Ok. Thanks a lot. In the dashboard most entries now are marked as "succeeded". However, I'm not able to access the recently archived repositories

If you give it a bit of time, that should eventually be browsable.
Internally, the webapp uses a replicated database.

Cheers,

Thanks for the explanation. The strange thing here is, that only the repository I requested to be archived are not yet browsable. Other requests (even much newer) are browsable for me

The first entry depicted in this screenshot is browsable, while one of mine requests (e.g. the fifth entry in the screenshot, https://github.com/Artalik/CompCert) not yet:

https://archive.softwareheritage.org/browse/origin/directory/?origin_url=https://github.com/getting-things-gnome/gtg

https://archive.softwareheritage.org/browse/origin/directory/?origin_url=https://github.com/Artalik/CompCert

fwiw, the urls mentioned are now browsable.

The strange thing here is, that only the repository I requested to be archived are not yet browsable. Other requests (even much newer) are browsable for me

There may be cache technologies in various layers in the equation as well, so that
might explain the apparent delays as well.

Cheers,

ardumont claimed this task.

This task led to an internal improvment so thanks for the heads up.

See the dedicated task [1] for details.

[1] T3367