Skip to content

feat(prepro): fix alignment ANY requirement - prepro should error if …#6413

Open
anna-parker wants to merge 2 commits into
mainfrom
prepro_alignment_any
Open

feat(prepro): fix alignment ANY requirement - prepro should error if …#6413
anna-parker wants to merge 2 commits into
mainfrom
prepro_alignment_any

Conversation

@anna-parker
Copy link
Copy Markdown
Contributor

@anna-parker anna-parker commented May 12, 2026

…the segment cant be assigned and warn if can be assigned but not aligned

resolves #

Screenshot

PR Checklist

  • All necessary documentation has been adapted.
  • The implemented feature is covered by appropriate, automated tests.
  • Any manual testing that has been done is documented (i.e. what exactly was tested?)

🚀 Preview: Add preview label to enable

…the segment cant be assigned and warn if can be assigned but not aligned
@anna-parker anna-parker requested a review from theosanderson May 12, 2026 18:01
@claude claude Bot added preprocessing Issues related to the preprocessing component deployment Code changes targetting the deployment infrastructure labels May 12, 2026
@theosanderson
Copy link
Copy Markdown
Member

@codex review

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 185fece775

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

)
)

return sequence_assignment
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep empty-segment submissions from passing classification

Returning immediately here drops the previous safeguard that emitted an error when sequence_assignment.unalignedNucleotideSequences stayed empty without any duplicate/unaligned diagnostics. In multi-segment mode, an entry with no uploaded nucleotide sequences now reaches later processing with no classification error, which can make a no-sequence submission look valid instead of being rejected with an explicit alignment/classification message.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If classification fails then nothing will align and the function alignment_errors_warnings will add an error so this should be fine

@theosanderson theosanderson added the preview Triggers a deployment to argocd label May 18, 2026
@anna-parker anna-parker removed the preview Triggers a deployment to argocd label May 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

deployment Code changes targetting the deployment infrastructure preprocessing Issues related to the preprocessing component

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants