Skip to content

Conversation

@BenTopping
Copy link
Contributor

@BenTopping BenTopping commented Oct 27, 2025

Closes #840

Changes proposed in this pull request

  • Adds useq_wafer table and draft of required columns, including lot number tracking columns
  • Adds useq_wafer model and tests

TODO

@codecov
Copy link

codecov bot commented Oct 27, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.00%. Comparing base (39bb4f3) to head (5fa86a3).
⚠️ Report is 10 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #841      +/-   ##
===========================================
+ Coverage    97.91%   98.00%   +0.08%     
===========================================
  Files           76       78       +2     
  Lines         1680     1755      +75     
===========================================
+ Hits          1645     1720      +75     
  Misses          35       35              
Flag Coverage Δ
pull_request 98.00% <100.00%> (+0.08%) ⬆️
push 98.00% <100.00%> (+0.08%) ⬆️
ruby 98.00% <100.00%> (+0.08%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@BenTopping BenTopping requested a review from sabrine33 October 28, 2025 15:18
sabrine33
sabrine33 previously approved these changes Oct 30, 2025
sabrine33
sabrine33 previously approved these changes Nov 5, 2025
t.datetime "otr_oil_expiry", precision: nil, comment: "Opentron oil expiry date"
t.string "otr_pipette_carousel", comment: "Opentron pipette carousel identifier"
t.string "otr_instrument_name", null: false, comment: "Opentron instrument name"
t.string "amp_assign_control_bead_tube", comment: "AMP assign control bead tube barcode"
Copy link
Contributor

Choose a reason for hiding this comment

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

Hi @BenTopping — I just realized that even when we mark some descriptors as required in SS, there’s no actual validation or check behind it. Essentially, a user can release a batch without filling in those required fields.

My concern is that if validation fails at the MLWH, the message will end up in the dead-letter queue silently. I’m not sure if it would be better to remove the NOT NULL constraints for the descriptor fields in this case.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh interesting..

Yes I can remove the validation for the time being.

Copy link
Contributor

@sabrine33 sabrine33 left a comment

Choose a reason for hiding this comment

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

Thanks @BenTopping

@BenTopping BenTopping merged commit c038fc9 into develop Nov 10, 2025
6 checks passed
@BenTopping BenTopping deleted the Y25-422-ultima-seq-table branch November 10, 2025 10:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Y25-422 - As a TL (Tom) I would like to create tables in the MLWH for Ultima sequencing to support and distinguish the new sequencing platform

3 participants