uros-b opened a new pull request, #57821:
URL: https://github.com/apache/spark/pull/57821

   ### What changes were proposed in this pull request?
   
   Fixes the scalafmt failure message in `dev/lint-scala`, which names the same 
path twice:
   
   ```
   The scalafmt check failed on sql/connect or sql/connect at following 
occurrences:
   ```
   
   The first path is corrected to `sql/api`, so the message reads `sql/api or 
sql/connect`.
   
   ### Why are the changes needed?
   
   The check runs over `sql/api` plus four modules under `sql/connect` 
(`common`, `server`, `shims`, `client/jvm`), so `sql/connect or sql/connect` is 
a tautology that tells the reader nothing about the first module. The corrected 
wording matches the `-pl` module list printed on the very next line of the same 
script.
   
   The duplication is a leftover of the module rename in SPARK-49428: the 
message previously read `sql/connect or connector/connect`, and applying the 
`connector/connect` to `sql/connect` rename to the message text collapsed both 
halves to the same path. The `sql/api` module had been added to the check 
earlier, in SPARK-49511, without the message being updated.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No. Developer-facing message text in a lint script only.
   
   ### How was this patch tested?
   
   No functional change. The edited string is inside an existing `echo -e` and 
no test, CI workflow, or doc matches on this message text, so nothing consumes 
it programmatically.
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (Opus 4.8)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to