Escape backslashes in DotGraph values#7606
Merged
labkey-tchad merged 2 commits intodevelopfrom Apr 22, 2026
Merged
Conversation
labkey-adam
approved these changes
Apr 21, 2026
Contributor
labkey-adam
left a comment
There was a problem hiding this comment.
Do we have any tests for this?
Member
Author
Not explicitly but |
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.
Rationale
We aren't escaping backslashes in our generated
DotGraph. This can end up generating invalid DOT syntax.The actual label in the following DOT snippet is intended to be
,\"^:}}"#)B-d@x.Db&-. We correctly escape the quote but not the backslash:The parser then decodes the double-backslash and leaves the following quote unescaped:
This is a pre-existing defect (reproduced in 25.7) but didn't cause any test failures because we didn't log errors returned by
dotexecution.Related Pull Requests
Changes