-
Notifications
You must be signed in to change notification settings - Fork 548
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
Failure to parse pyproject.toml file when run on Windows #935
Comments
Hello @nfelt14, |
This issue is fixed by #938 or additional change is required ? |
Hello👋, |
The the commit actions/setup-python@29a37be over 5.2.0 because it include a fix the windows system that doesn't handle CRLF well. The reason for this is `actions/setup-python` is looking for project to test that change: actions/setup-python#935 (comment)
The the commit actions/setup-python@29a37be over 5.2.0 because it include a fix the windows system that doesn't handle CRLF well. The reason for this is `actions/setup-python` is looking for project to test that change: actions/setup-python#935 (comment)
Hello @priya-kinthali I've updated our workflows to use the commit 29a37be in Scille/parsec-cloud@644618d At least where the update to |
Hello @nfelt14 👋, |
Yes, I just confirmed that this works on the main branch. |
Thankyou for the update! |
On Windows, the action fails with invalid ctrl chars in comments. See actions/setup-python#935. Remember to revert to v5 when v5.3 is released.
Description:
The action is failing with this error message when run on a Windows runner.
Action version:
I believe that it is v5.2.0
Platform:
Runner type:
Tools version:
Repro steps:
Workflow run: https://github.com/tektronix/tm_devices/actions/runs/10624903656/job/29454004640?pr=293
Here is a snippet of the toml file that is failing to be read:
Expected behavior:
I expect it to parse the toml file the same way that it works on Ubuntu and MacOS.
Actual behavior:
The file is unable to be parsed due to a false failure for a character that doesn't seem to actually be there.
The text was updated successfully, but these errors were encountered: