For some COBs, parent commits can be specified for actions, for example, patches will bundle their base and head commits as parents.
When the COB stream performs the revwalk, these commits will be included, and will not have the manifest file – resulting in an error.
Instead, this error can be matched against, and the commit is skipped instead. The other errors should still be resurfaced, since a commit with a manifest should be expected to load the operation correctly, and the commit should exist in the repository when attempting to load it.
One might argue that a valid operation with a missing manifest could
occur, but that would mean that radicle-cob has performed an invalid
write. This is undetectable by the stream API, and is ambiguous with
the case of non-Op commits.
For some COBs, parent commits can be specified for actions, for example, patches will bundle their base and head commits as parents.
When the COB stream performs the revwalk, these commits will be included, and will not have the manifest file – resulting in an error.
Instead, this error can be matched against, and the commit is skipped instead. The other errors should still be resurfaced, since a commit with a manifest should be expected to load the operation correctly, and the commit should exist in the repository when attempting to load it.
One might argue that a valid operation with a missing manifest could
occur, but that would mean that radicle-cob has performed an invalid
write. This is undetectable by the stream API, and is ambiguous with
the case of non-Op commits.