Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Handle CRLF line endings in plugin meta.yamls
See original GitHub issueIs your enhancement related to a problem? Please describe.
Currently the plugin registry build expects plugin metas to have linux line endings (LF). This can cause problems building the registry on Windows, where line endings may be converted automatically. We should improve our scripts to accommodate CRLF line endings as well.
Additional info
https://github.com/eclipse/che/issues/14807#issuecomment-539976839
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Git replacing LF with CRLF - windows - Stack Overflow
The concept of autocrlf is to handle line endings conversions transparently. And it does! Bad news: the value needs to be configured manually....
Read more >warning: LF will be replaced by CRLF and Special characters ...
warning: LF will be replaced by CRLF in .buffalo.dev.yml. The file will have its original line endings in your working directory.
Read more >Resolved: Git warning LF will be replaced by CRLF in file
warning: LF will be replaced by CRLF in ansible.cfg. The file will have its original line endings in your working directory.
Read more >CRLF vs. LF: Normalizing Line Endings in Git
Line endings can differ from one OS to another. Learn the history behind CRLF and LF line endings and how to enforce line...
Read more >Files and paths on Windows - Puppet
Puppet and Windows handle directory separators and line endings in files somewhat differently, so you must be aware of the differences when you...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
can it be solved also by setting the git config line endings ?
This is no longer a problem – we no longer let users write their own meta.yamls, they are generated automatically.