huseyincansoylu
huseyincansoylu2mo ago

deno install not working on latest canary

mac version: Apple M1 Pro deno version: deno 2.0.0-rc.1+f0a3d20
moonrepoV3 git:(main) ✗ deno upgrade --canary
Current Deno version: v1.46.3
Looking up canary version

Found latest canary version f0a3d206422af3177e0f36ed22802c1ccc6f7654

Downloading https://dl.deno.land/canary/f0a3d206422af3177e0f36ed22802c1ccc6f7654/deno-aarch64-apple-darwin.zip
Deno is upgrading to version f0a3d206422af3177e0f36ed22802c1ccc6f7654

Upgraded successfully to Deno f0a3d206422af3177e0f36ed22802c1ccc6f7654 (canary)

moonrepoV3 git:(main) ✗ deno install
error: No such file or directory (os error 2), symlink '../../../../../node_modules/.deno/svelte@4.2.12/node_modules/svelte' -> '/Users/cansoylu/Projects/moonrepoV3/apps/opsap/clients/mobile/node_modules/svelte'
moonrepoV3 git:(main) ✗ deno upgrade --canary
Current Deno version: v1.46.3
Looking up canary version

Found latest canary version f0a3d206422af3177e0f36ed22802c1ccc6f7654

Downloading https://dl.deno.land/canary/f0a3d206422af3177e0f36ed22802c1ccc6f7654/deno-aarch64-apple-darwin.zip
Deno is upgrading to version f0a3d206422af3177e0f36ed22802c1ccc6f7654

Upgraded successfully to Deno f0a3d206422af3177e0f36ed22802c1ccc6f7654 (canary)

moonrepoV3 git:(main) ✗ deno install
error: No such file or directory (os error 2), symlink '../../../../../node_modules/.deno/svelte@4.2.12/node_modules/svelte' -> '/Users/cansoylu/Projects/moonrepoV3/apps/opsap/clients/mobile/node_modules/svelte'
you can test this out on github: https://github.com/zemili-group/moonrepoV3
GitHub
GitHub - zemili-group/moonrepoV3: Deno monorepo on deno deploy all ...
Deno monorepo on deno deploy all things zemil-group - zemili-group/moonrepoV3
21 Replies
marvinh.
marvinh.2mo ago
That definitely shouldn't happen. Filed an issue for it https://github.com/denoland/deno/issues/25493
huseyincansoylu
huseyincansoylu2mo ago
how can i upgrade to a previous canary release ? where can i find a list of commit hashes ? can you show me the command to run upgrade to spesific commits ? thanks so much @marvinh.
marvinh.
marvinh.2mo ago
You can find a list of commit hashes on GitHub (those random letters at the right) https://github.com/denoland/deno/commits/main/ You can upgrade to any commit by running deno upgrade <commit-sha>
huseyincansoylu
huseyincansoylu2mo ago
i am not sure if its correct 🤔
No description
Sean Knowles
Sean Knowles2mo ago
Did this work, it says it didn't find any download after passing in a commit hash?
No description
huseyincansoylu
huseyincansoylu2mo ago
yeah i have the same issue @Sean Knowles
Sean Knowles
Sean Knowles2mo ago
Not sure if we are having any luck here, can't get passed the error @marvinh.
bartlomieju
bartlomieju2mo ago
You need to pass the full hash, not the short hash Click the button next to a hash on GitHub to copy it I'll improve that error message Is there a green checkmark next to that commit on GitHub? If not it will not work
Sean Knowles
Sean Knowles2mo ago
Okay great thanks will double check that in future Thanks @bartlomieju Looks like the PR is ready on this? If its merged can we use it on canary immediately?
bartlomieju
bartlomieju2mo ago
No, it needs to land on main and you need to wait some time before CI passes. Depending on your os/arch it can be anywhere between 30m and 2h You can also downgrade to the version before the problematic change for the time being
Sean Knowles
Sean Knowles2mo ago
I've been trying to... No luck!
bartlomieju
bartlomieju2mo ago
Have you tried e27a19c02c537626d7874f7521f4e39d6dfad0af?
Sean Knowles
Sean Knowles2mo ago
not yet Will try now
bartlomieju
bartlomieju2mo ago
@nathanwhit could you please take a look and advise which commit to use?
Sean Knowles
Sean Knowles2mo ago
didn't work
Sean Knowles
Sean Knowles2mo ago
No description
Sean Knowles
Sean Knowles2mo ago
seanknowles@ip-192-168-138-254 ‹ main ● › : ~/Projects/Zemili/moonrepoV3
[0] % deno -v
deno 2.0.0-rc.0+e27a19c
seanknowles@ip-192-168-138-254 ‹ main ● › : ~/Projects/Zemili/moonrepoV3
[0] % deno -v
deno 2.0.0-rc.0+e27a19c
nathanwhit
nathanwhit2mo ago
The commit before the bug was introduced is ef1294e4e5beb68676ba64a6c3a44ff0a277e68a, but that's on 1.46.1 so it might be too old if you're already using 2.0 features. The PR to fix the bug will land whenever CI finishes, and then once CI on main is done the canary with the fix will be available. It'll probably be 1-2 hours from now
Sean Knowles
Sean Knowles2mo ago
Legendary Again, thanks so much for such a quick fix! Cheers guys
nathanwhit
nathanwhit2mo ago
The fixed canary is now available! If you do deno upgrade canary you should get the new version. Feel free to try it out and let me know if it works for you now
huseyincansoylu
huseyincansoylu2mo ago
It worked! Thanks for the quick fix