construct-hub
construct-hub copied to clipboard
Identify missing packages
For various reasons, it might be the case that messages were lost from the pipeline before properly ingested.
Right now, if a package was discovered and staged, but was lost before it was ingested, we have no way to recover that package apart from doing a complete backfill from npm.
This is because the re-process workflow only operates on packages that were ingested.
We should have a way to detect packages that were discovered, but never ingested, and re-ingest them.
How does a package get lost after staging but before it is was ingested? Shouldn't such a package end up in the Staging DLQ?
@iliapolo are you still working on this issue?
Nope. Never really started...unassigning
This issue is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon. If you wish to exclude this issue from being marked as stale, add the "backlog" label.