-
Notifications
You must be signed in to change notification settings - Fork 6
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
spin build --up fails because project-name in template wasn't instantiated #12
Comments
I'm not quite sure what's going on here. It seems like some people are seeing that when Cargo tries to build a Git reference it picks up files that are not part of the crate. @benwis mentioned he saw the message but it didn't prevent the build. And I'm not seeing it at all. @Boscop Could you share what version of Cargo you're running please? @dicej @rylev Do you have any idea why this might be happening? |
I think we'll need a more consistent way to reproduce this before being able to say what the root cause is. |
I'll try to give more details As he said, everything still builds and deploys fine for me, those messages just seem odd. My rudimentary theory is that they're coming from rust itself, and may be an issue with nightly? |
For me it's also failing because this syntax of setting env vars doesn't work on windows:
Is there a platform-agnostic way to write this build command? Or is it possible to remove the need for having this env var in the first place? :) Btw, I see |
Btw, But calling
Could it be that the downloaded file's target path contains chars that are invalid in a windows path? |
@Boscop Yes, I'm afraid that Re the error when deploying from Windows: this was meant to be fixed by fermyon/spin#2159 but the cloud plugin (which |
@Boscop I've reproduced your problem - the |
@Boscop cloud deploy fix is out. Please run
You should then have cloud plugin 0.6.1 and your Windows deploys should work! Sorry for the inconvenience. |
Thanks, it worked :) |
Not yet I'm afraid. We've chatted about allowing |
The text was updated successfully, but these errors were encountered: