-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re ingest missing packages #536
Comments
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. |
Resolves #536 Adds a new lambda function intended for manual invocation. This function will re-attempt to stage a specific package version. Documented usage in the runbook. I need to upgrade the node types to node18 for this, which required some additional type only changes w.r.t the SDKv3 usage. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
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.
The text was updated successfully, but these errors were encountered: