<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=413983) </details> <!--IssueSummary end--> <!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary The Web IDE displays files with CRLF endings as though they are LF. With terraform projects it does not matter for *MOST* files. However, when a terraform provider enables pushing the file to a client, some parts of Windows may be sensitive to line endings - notably PowerShell, which is used as a Windows automation language. I am seeing some evidence it may also be using UTF-16 encoding rather than the UTF-8 indicated in the UI. ### Steps to reproduce 1. Create or change a file to CRLF file endings. Change can be done by clicking line ending type in the status bar. 1. Notice that saving the file causes a commit to be necessary (git detected the diff) 2. Ensure .gitattributes forces the file type to "CRLF" on checkout with ```` *.ps1 text eol=crlf ```` 3. optionally force a workspace setting for vs code for new files in the project ``` { "files.eol": "\r\n" } ``` 4. Commit the file - the character display at the bottom of the screen changes from CRLF to LF 5. Check the file out on another machine 6. Use cat -ve to see that the file is actually "CRLF" (ends of lines contain "M$" rather than just "$"). ### Example Project <!-- If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report. If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version. --> ### What is the current *bug* behavior? Web IDE always reverts to displaying "LF" line ending, even for files saved with "CRLF" ### What is the expected *correct* behavior? Web IDE correctly reads and displays actual line endings. ### Relevant logs and/or screenshots     ### Output of checks <!-- If you are reporting a bug on GitLab.com, uncomment below --> <!-- This bug happens on GitLab.com --> <!-- /label ~"reproduced on GitLab.com" --> #### Results of GitLab environment info <!-- Input any relevant GitLab environment information if needed. --> <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`) </pre> </details> #### Results of GitLab application Check <!-- Input any relevant GitLab application check information if needed. --> <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:check SANITIZE=true`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`) (we will only investigate if the tests are passing) </pre> </details> ### Possible fixes <!-- If you can, link to the line of code that might be responsible for the problem. -->