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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: windows dagger init command #7003

Merged
merged 5 commits into from
Apr 16, 2024
Merged

Conversation

jedevc
Copy link
Member

@jedevc jedevc commented Apr 3, 2024

Fixes #6923 馃帀

Warning

Depends on tonistiigi/fsutil#196

Still needs some tidy-ups, but I managed to actually get this working on windows again!

Love filepaths. So fun.

image

@jedevc jedevc added this to the v0.11.1 milestone Apr 8, 2024
@jedevc jedevc force-pushed the fix-windows-dagger-init branch 2 times, most recently from ed45198 to f33cbbb Compare April 9, 2024 14:11
@jedevc jedevc marked this pull request as ready for review April 9, 2024 14:11
@jedevc jedevc requested a review from sipsma April 9, 2024 14:11
@@ -924,7 +924,7 @@ func (s *moduleSchema) collectCallerLocalDeps(
return nil, fmt.Errorf("error unmarshaling config at %s: %s", configPath, err)
}

case strings.Contains(err.Error(), "no such file or directory"):
case strings.Contains(err.Error(), "no such file or directory") || strings.Contains(err.Error(), "not found"):
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah this is fun 馃槃 there's just different error message strings depending on whether the client is linux/windows.

I can't think of a neat way round this really.

core/schema/modulesource.go Outdated Show resolved Hide resolved
Signed-off-by: Justin Chadwell <me@jedevc.com>
Signed-off-by: Justin Chadwell <me@jedevc.com>
Previously, license searching might escape the context - this was weird.

Signed-off-by: Justin Chadwell <me@jedevc.com>
Signed-off-by: Justin Chadwell <me@jedevc.com>
@jedevc jedevc merged commit 51562bf into dagger:main Apr 16, 2024
12 of 13 checks passed
@jedevc jedevc deleted the fix-windows-dagger-init branch April 16, 2024 10:44
vikram-dagger pushed a commit to vikram-dagger/dagger that referenced this pull request May 3, 2024
* fix: windows dagger init command

Signed-off-by: Justin Chadwell <me@jedevc.com>

* chore: simplify client file accessors

Signed-off-by: Justin Chadwell <me@jedevc.com>

* fix: ensure license searching doesn't go above context

Previously, license searching might escape the context - this was weird.

Signed-off-by: Justin Chadwell <me@jedevc.com>

* chore: remove old commented out code

Signed-off-by: Justin Chadwell <me@jedevc.com>

---------

Signed-off-by: Justin Chadwell <me@jedevc.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

馃悶 Dagger init can't run on windows
2 participants