StudyDatasetsTest fix for importing tsv data with a field name that contains double quote#6874
Merged
cnathe merged 1 commit intorelease25.7-SNAPSHOTfrom Jul 24, 2025
Merged
Conversation
…ontains double quote - use teh TestDataUtils.tsvStringFromRowMaps() helper instead of generating a tab sep string in the test case
labkey-danield
approved these changes
Jul 24, 2025
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
2 participants
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.
Rationale
This is a backport of a test change so that we don't continue to get this failure randomly in 25.7. When the StudyDatasetsTest fuzz testing randomly generates a field name containing a double quote, it is failing the tsv import because the quote isn't encoded in the tsv import.
Related Pull Requests
Changes