Change Details

This is an issue most possibly encountered mostly on staging. But technically, the error could happen in production as snapshot_get_all_branches could return None as well (ignored, if it happens, Snapshot.from_dict raises). As we can mount partial dump from production, not everything exists. Typically, here dangling snapshots from origin visits currently. This ensures we can use staging nonetheless. Related to T2428 https://sentry.softwareheritage.org/share/issue/4eb69ea2cc314c4ab811809ff60c358f/

This is an issue most possibly encountered only on staging. But technically, the error could happen in production as snapshot_get_all_branches could return None as well (which is currently ignored). If that happens though, `Snapshot.from_dict` raises. Most proeminent in staging, because we can mount partial dump from production. Thus not everything exists. Typically, recently the error is raised because of dangling snapshots from origin visits. So thix fix ensures we can use staging nonetheless. Related to T2428 https://sentry.softwareheritage.org/share/issue/4eb69ea2cc314c4ab811809ff60c358f/

This is an issue most possibly encountered mostonly on staging. But technically, the error could happen in production as snapshot_get_all_branches could return None as well (which is currently ignored,). if iIf that happens though, `Snapshot.from_dict` raises). As we can mount partial dump fromMost production, not everything exists.eminent in staging, Typically,because we can mount partial dump from production. here dangling snapshots from origin visits currently.Thus not everything exists. Typically, This ensures we can userecently the error is raised because of dangling snapshots from origin visits. So thix fix ensures we can use staging nonetheless. Related to T2428 https://sentry.softwareheritage.org/share/issue/4eb69ea2cc314c4ab811809ff60c358f/