Skip to content
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

Augment EOL Check to catch missing newline at EOF #496

Closed
dilijev opened this issue Mar 9, 2016 · 12 comments
Closed

Augment EOL Check to catch missing newline at EOF #496

dilijev opened this issue Mar 9, 2016 · 12 comments

Comments

@dilijev
Copy link
Contributor

dilijev commented Mar 9, 2016

Ensure that the check includes exceptions for tool-generated (or tool-modified) files like .sln and .vcxproj.

@srs88
Copy link

srs88 commented Sep 28, 2017

Hi @dilijev, Are you still looking for a fix for this issue?

@dilijev
Copy link
Contributor Author

dilijev commented Sep 28, 2017

@srs88 Sure! Want to take a crack at it?

@srs88
Copy link

srs88 commented Sep 29, 2017

Yes! I am a student trying to learn the codebase. Can you give me some pointers to start with?

@dilijev
Copy link
Contributor Author

dilijev commented Sep 29, 2017

For this one you'll basically just need to look at
https://github.com/Microsoft/ChakraCore/tree/master/jenkins

Files: check_*.sh

You just need to follow the patterns there, come up with a way to detect whether each (non-excluded) file has the last character in the file as a line feed (0x0a). This issue suggests such a check would make sense as additional logic in check_file_eol.sh

The list of files (and excluded files) are computed here: https://github.com/Microsoft/ChakraCore/blob/master/jenkins/check_eol.sh#L18
and the list is sent to check_file_eol.sh (one at a time).

@dilijev
Copy link
Contributor Author

dilijev commented Sep 29, 2017

When you submit a PR, your check will run automatically because Jenkins is already configured to run check_eol.sh as a task.

As part of your change you'll have to correct any files which are incorrect so that you pass your own new check! You'll also have confirmation about whether it's working.

Please try to verify your check by running it on your own computer first.

@srs88
Copy link

srs88 commented Oct 2, 2017

Thank you for the tips. I will try and get back to you.

@dilijev
Copy link
Contributor Author

dilijev commented Jan 17, 2018

@srs88 wondering if you've had any success?

@srs88
Copy link

srs88 commented Jan 18, 2018

Hi @dilijev. My apologies. I got busy with my course work and missed this. I will try this today.

@dilijev
Copy link
Contributor Author

dilijev commented Jan 18, 2018

@srs88 no pressure! :) Let us know if you need any help. Feel free to reach out on https://gitter.im/Microsoft/ChakraCore

@rhuanjl
Copy link
Collaborator

rhuanjl commented Aug 10, 2018

I've made a PR to respond to this #5583

@MSLaguana
Copy link
Contributor

I think you mean #5583

@rhuanjl
Copy link
Collaborator

rhuanjl commented Aug 10, 2018

@MSLaguana indeed, sorry for the typo and thanks for the correction (fixed above)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants