-
Notifications
You must be signed in to change notification settings - Fork 2
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
Ingest add revocation comment #2451
base: main
Are you sure you want to change the base?
Conversation
d26298c
to
a8cca4b
Compare
8a3a51f
to
c9cef11
Compare
c9cef11
to
a1ef9f0
Compare
d35a1ad
to
60ec5a2
Compare
It would be nice to merge this before #2651 |
60ec5a2
to
5cd068c
Compare
…oject/loculus into ingest_add_revocation_comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me in terms of readability,etc.! Thanks! In terms of being confident it works:
(A) I presume you have tested it out in some way?
(B) At some point pretty soon we should add code tests for all of this - but it seems mean to do that in this PR specifically :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How is regroup defined? We could in principle not revoke If the change is simply addition of a new segment to an existing segment.
Have you tested revoke with something like: run ingest with sorted authors, then ingest with unsorted authors. That should show some revokes.
The functions were added with ingest tests in #2372.
I have only tested with the test examples (and some modifications of the test examples) in the ingest
At the moment revoke_and_regroup will always revoke the old group and create a new group. I realized handling different cases gets very complicated quickly and as this is such an edge case anyways I didn't think it made sense to go into details yet. That is also why I made revoke_and_regroup only run with manual approval. We can look into the cases and handle them differently if we would like to. |
resolves #
preview URL: https://ingest-add-revocation-com.loculus.org/
Summary
Add description of why sequence has been revoked if revoked due to grouping changes
Screenshot
PR Checklist