[SPARK-54857][WEBUI][TESTS] Add test ensuring user name and app name in historypage get escaped #53628
+108
−15
Conversation
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
sarutak
commented
Dec 27, 2025
| "id" : "application_1628109047826_1317105", | ||
| "name" : "Spark shell" | ||
| }, { | ||
| "attempts" : [ { |
Member
Author
There was a problem hiding this comment.
This entry is removed when generating the golden file as the number of entries is expected to be three.
HyukjinKwon
approved these changes
Dec 29, 2025
Member
Author
|
Merged to |
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.
What changes were proposed in this pull request?
This PR proposes to add tests for SPARK-53337 and SPARK-54624.
Why are the changes needed?
To ensure user name and app name in historypage get escaped.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Add new test.
Was this patch authored or co-authored using generative AI tooling?
No.