-
Notifications
You must be signed in to change notification settings - Fork 28.8k
[SPARK-3758] Script style checking #2612
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
QA tests have started for PR 2612 at commit
|
QA tests have finished for PR 2612 at commit
|
Test PASSed. |
Does this actually cause an issue in practice? We run tests on windows for each release. I'm worried since most of us develop on mac/linux that this will end up in a weird state where there are mixed EOL characters. |
I've not seen issues related to EOL characters in Spark yet but I saw issues in other projects. One of the cases is in Jenkins. https://issues.jenkins-ci.org/browse/JENKINS-7478 In Spark, we may not have issues like JENKINS-7478 but I'm afraid that we have unexpected problems caused by LF-only EOL. We cannot know what's happen when we use wrong EOL. Do you mean you want to avoid both LF and CRLF are contained in one file right? |
@pwendell Actually, CRLF is already contained in compute-classpath.cmd so I think, we should unify CRLF or LF in *.cmd. |
Generally, using LF as EOL character of *.cmd files may cause some troubles. I know *.cmd with LF runs seemingly well in many cases, but sometimes cause inexplicable trouble because LF is defenetely not the proper EOL character of Windows *.cmd files. |
QA tests have started for PR 2612 at commit
|
QA tests have finished for PR 2612 at commit
|
Test PASSed. |
I'd worry about this, too. If one of us edits one of these files on a Mac, we might unknowingly recreate the issue this PR is trying to fix. Does it make sense to add some kind of style check to |
Thanks @nchammas . |
QA tests have started for PR 2612 at commit
|
Test FAILed. |
QA tests have started for PR 2612 at commit
|
Test PASSed. |
QA tests have started for PR 2612 at commit
|
Test PASSed. |
Test FAILed. |
retest this please. |
QA tests have started for PR 2612 at commit
|
QA tests have finished for PR 2612 at commit
|
Test PASSed. |
QA tests have started for PR 2612 at commit
|
QA tests have finished for PR 2612 at commit
|
Test FAILed. |
I noticed .gitattributes should be merged before this PR otherwise the rules defined in .gitattributes doesn't applied. |
@pwendell Because of the reason I mentioned above, I intend to split this PR (for .gitattributes and for style-checking). |
QA tests have started for PR 2612 at commit
|
QA tests have finished for PR 2612 at commit
|
Test FAILed. |
QA tests have started for PR 2612 at commit
|
QA tests have finished for PR 2612 at commit
|
Test PASSed. |
QA tests have started for PR 2612 at commit
|
QA tests have finished for PR 2612 at commit
|
Test FAILed. |
QA tests have started for PR 2612 at commit
|
QA tests have finished for PR 2612 at commit
|
Test PASSed. |
Given that no one seems super interested in this refactoring, I'll close this issue as a wontfix. If someone wants to come and revive it later, please feel free. |
O.K, I'll close this PR for now. |
There are no way to check style of scripts.