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
[turborepo] turbo prune throws unable to parse yaml: data did not match any variant of untagged enum StringOrNum #4925
Comments
We are seeing the same issue with the latest version, yarn v3 node_module linker |
Just got the same issue while deploying to Vercel, also using yarn 3 with node_modules linker. |
Same. |
Oh good! I'm not the only one. Using yarn v3 with node_modules linker and turbo 1.9.4 |
I'm also facing this error in the context of
I validated that with
This part in match StringOrNum::deserialize(deserializer)? {
StringOrNum::String(s) => Ok(SemverString(s)),
StringOrNum::Num(x) => Ok(SemverString(x.to_string())),
} |
Hello sorry for the disruption. Could someone section of the |
All good, thanks for your work on improving this great tool! 😄
|
Hmm, the line number of the parse error seems to be off, that metadata matches one of the fixtures we tested parsing against. Is there any way you could share your lockfile with me? |
Not immediately, sorry. I'd need to discuss with legal first and this might take a bit... If you can point me to the place where I could add more logging within turbo, I should be able to compile it locally, use it on the failing |
No worries, I'm pretty sure I just found the issue. Should have a fix up soon. |
### Description I believe this is probably the culprit behind #4925. `serde_yaml` parses `1` as an unsigned int, `1.2` as a float, and `1.2.3` as a string. We were missing handling the float case. ### Testing Instructions Added unit test of deserialization of semver ranges that's a valid float
I'm getting the same # This file is generated by running "yarn install" inside your project.
# Manual changes might be lost - proceed with caution!
__metadata:
version: 6
cacheKey: 8 |
I confirm that #4945 is solving the issue. |
i can confirm the issue is resolver in v1.9.7-canary.0. I guess issue can be closed once Thanks @chris-olszewski and all 🤝 |
What version of Turborepo are you using?
1.9.4
What package manager are you using / does the bug impact?
Yarn v2/v3 (node_modules linker only)
What operating system are you using?
Mac
Describe the Bug
running
yarn dlx turbo prune --scope=myapp
throws:the same will work just fine with v1.9.3
I'm not sure which yaml file is referring to, i'm guessing is something internally in turbo?
Expected Behavior
yarn dlx turbo prune --scope=myapp
won't throw errors.To Reproduce
yarn dlx turbo prune --scope=myapp
Reproduction Repo
No response
The text was updated successfully, but these errors were encountered: