Page MenuHomeSoftware Heritage

Add support for "uninterpreted upstream object" in SWH model and storage
Open, LowPublic

Description

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".

Event Timeline

douardda renamed this task from Add support for "uninterpreted upstream object" in our model and storage to Add support for "uninterpreted upstream object" in SWH model and storage.Apr 22 2021, 2:33 PM
douardda claimed this task.

Same as T1957

actually no, it's not the same...