[MINOR][HOTFIX] Wrap overlong comment line in JDBCSuite to fix scalastyle#56446
Closed
viirya wants to merge 1 commit into
Closed
[MINOR][HOTFIX] Wrap overlong comment line in JDBCSuite to fix scalastyle#56446viirya wants to merge 1 commit into
viirya wants to merge 1 commit into
Conversation
…tyle SPARK-57332 (f5eabcb) introduced a 103-character comment line in JDBCSuite.scala, breaking the scalastyle line-length check (max 100) and failing the lint job for master and every open PR. Rewrap the comment. Co-authored-by: Claude Code
Member
Author
|
#56441 already opens to fix it. |
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
1 participant
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?
Rewraps a 103-character comment line in
JDBCSuite.scalaintroduced by SPARK-57332 (f5eabcb) so it fits the 100-character scalastyle limit. Comment-only change.Why are the changes needed?
The overlong line fails
dev/scalastyle, so the "Linters, licenses, and dependencies" job is currently red on master and on every open PR (PR CI merges with the latest master before running).Does this PR introduce any user-facing change?
No.
How was this patch tested?
Verified no non-import line in the file exceeds 100 characters.
Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Code