LIMS-2040: Fix bug creating more than one puck#1019
Merged
ndg63276 merged 1 commit intopre-release/2026-R1.3from Feb 3, 2026
Merged
LIMS-2040: Fix bug creating more than one puck#1019ndg63276 merged 1 commit intopre-release/2026-R1.3from
ndg63276 merged 1 commit intopre-release/2026-R1.3from
Conversation
gfrn
approved these changes
Jan 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
JIRA ticket: LIMS-2040
Summary:
Creating a puck, and then creating another, gives an internal server error. This was introduced by #965, as parentContainerId and parentContainerLocation are reset to empty strings between pucks, rather than nulls. The backend also doesn't sanitise the input, so the database throws an error.
Changes:
To test: