loaders sometime find a revision or a release that are valid DVCS objects (ie. valid git object) but we cannot represent due to limitations of out model.
The typical example that comes to mind are revisions which commit date is out of range (see examples in T3170 and T3200).
The idea would be to keep track of these objects and prevent to "break the graph".
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Unknown Object (Maniphest Task) | ||||
| Migrated | gitlab-migration | T367 ingest Google Code repositories | ||
| Migrated | gitlab-migration | T617 ingest Google Code Subversion repositories | ||
| Unknown Object (Maniphest Task) | ||||
| Unknown Object (Maniphest Task) | ||||
| Unknown Object (Maniphest Task) | ||||
| Migrated | gitlab-migration | T328 svn / subversion loader | ||
| Migrated | gitlab-migration | T611 support for external definitions in the svn/subversion loader | ||
| Migrated | gitlab-migration | T1617 Experiment with generation numbers to improve revisions walk performance | ||
| Migrated | gitlab-migration | T1957 Handling missing DAG nodes | ||
| Migrated | gitlab-migration | T3282 Add support for "uninterpreted upstream object" in SWH model and storage |