-
-
Notifications
You must be signed in to change notification settings - Fork 105
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
Vendor Pull Operation Does Not Work on Windows #832
Comments
We'll look into this, thanks for reporting! |
This should be resolved in 1.128.0 |
I wanted to come back and say that this scenario still fails: I found that it's tied to the included_paths. Looks like it could be the same as this issue: I'll track the other issue for resolution. Thanks again for the quick fix for Windows! 🚀 |
@aclarke822 can you confirm the precise version of Atmos you tested? If you have a vendor config we can use to reproduce (and add to our tests), that will speed it up. Note, we are now testing on windows in our CI pipelines, so we can confirm vendoring does work in the general sense; there must be something about your configuration we are not testing. |
I tested on 1.20.0 and 1.133.0. Here is an example freshly tested on 1.133.0: Files from: vpcC successfully pulls the files. All other sources appear successful based on CLI output, but result in empty directories. The only difference between them (other than naming) is the included_paths property. |
Describe the Bug
When attempting the vendor pull operation on Windows 11, at least 2 scenarios fail.
With a github source and no version specified, no error is thrown but the resulting directory is empty.
With a github source and a version specified, CreateFile operation fails with:
CreateFile ~\AppData\Local\Temp\1733760752881339476/vpc?ref=1.398.0: The filename, directory name, or volume label syntax is incorrect.
The same scenarios were tested on Amazon Linux (al2023-ami-2023.5.20240722.0-kernel-6.1-x86_64) with no issues.
Expected Behavior
The vendor pull operation should vendor the modules and clone them to the appropriate directories.
Steps to Reproduce
Use the vendor.yaml provided in the quickstart guides and run
atmos vendor pull
on Windows.Screenshots
No response
Environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: