bun
bun copied to clipboard
Internal Assertion Failure: Invalid cache key "\wsl.localhost"
What version of Bun is running?
1.1.3
What platform is your computer?
Microsoft Windows [versão 10.0.22631.3447]
What steps can reproduce the bug?
Hello, can anyone help me? I'm trying to create the Bun Next APP in the new version 1.1.3 but it's not working and this error is appearing:
I managed to install it but I can't use the commands in vs code ''bun create-next-app@latest .'', "bun create next-app" "bunx --bun create-next-app@latest my-app --typescript --tailwind --eslint"
"uh-oh: Internal Assertion Failure: Invalid cache key "\wsl.localhost"
See Resolver.assertValidCacheKey for details.
bun will crash now 😭😭😭
----- bun goal -----
Bun v1.1.3 (2615dc74) Windows x64 (baseline)
CreateCommand:
Elapsed: 9ms | User: 0ms | Sys: 0ms
RSS: 20.02MB | Peak: 20.02MB | Commit: 62.65MB | Faults: 5019
----- bun goal -----
0 00007FF6A6391F58
1 ???
two ???
3 ???
4 ???
5 ???
6 ???
7 ???
8 ???
9 ???
10???
11 ???
12???
Search GitHub issues https://bun.sh/issues or join in windows channel in https://bun.sh/discord
thread 21368 panic: Internal Assertion Failure: Invalid cache key "\wsl.localhost"
See Resolver.assertValidCacheKey for details.
???:?:?: 0x7ff6a5259c34 in ??? (bun.exe)
???:?:?: 0x7ff6a505c908 in ??? (bun.exe)
???:?:?: 0x7ff6a4d4e3e8 in ??? (bun.exe)
???:?:?: 0x7ff6a4d4906f in ??? (bun.exe)
???:?:?: 0x7ff6a4eda89a in ??? (bun.exe)
???:?:?: 0x7ff6a4f35ac8 in ??? (bun.exe)
???:?:?: 0x7ff6a4fc4a23 in ??? (bun.exe)
???:?:?: 0x7ff6a4d015fe in ??? (bun.exe)
???:?:?: 0x7ff6a788cce3 in ??? (bun.exe)
???:?:?: 0x7ff996e4257c in ??? (KERNEL32.DLL)
???:?:?: 0x7ff998eaaa47 in ??? (ntdll.dll)"
And it also gave this error:
error: bunx failed to install create-next-app@latest due to error:
ECHILD: No child processes (waitpid())
What is the expected behavior?
No response
What do you see instead?
No response
Additional information
And it also gave this error:
error: bunx failed to install create-next-app@latest due to error: ECHILD: No child processes (waitpid())
I have the same issue, I installed bun 1.1.4 on both windows11 and WSL2 for ubuntu. It was still normal in WSL2 a few days ago. As for Bundows? It has never worked on my device.
I seem to have found the source of this issue. When I use bun i
in WSL2, it is reading the bun installed in windows, not the bun I installed in WSL2. When I remove Bundows everything runs smoothly.
Could you explain better how I could do this step by step to work?
On Thu, 18 Apr 2024 at 11:37 aiktb @.***> wrote:
I seem to have found the source of this issue. When I use bun i in WSL2, it is reading the bun installed in windows, not the bun I installed in WSL2. When I remove Bundows everything runs smoothly.
— Reply to this email directly, view it on GitHub https://github.com/oven-sh/bun/issues/10281#issuecomment-2064037609, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDVQCWDZGXIB6KPQVWT7URLY57LBZAVCNFSM6AAAAABGHS3QTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRUGAZTONRQHE . You are receiving this because you authored the thread.Message ID: @.***>
Could you explain better how I could do this step by step to work? … On Thu, 18 Apr 2024 at 11:37 aiktb @.> wrote: I seem to have found the source of this issue. When I use bun i in WSL2, it is reading the bun installed in windows, not the bun I installed in WSL2. When I remove Bundows everything runs smoothly. — Reply to this email directly, view it on GitHub <#10281 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDVQCWDZGXIB6KPQVWT7URLY57LBZAVCNFSM6AAAAABGHS3QTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRUGAZTONRQHE . You are receiving this because you authored the thread.Message ID: @.>
I have Bun installed in both windows and WSL2. I run Bun in WSL2, not windows, but I get the same error as you, I think it's some sort of conflict between the two versions of Bun, try removing one of them to see if it works.
Could you explain better how I could do this step by step to work? … On Thu, 18 Apr 2024 at 11:37 aiktb @.> wrote: I seem to have found the source of this issue. When I use bun i in WSL2, it is reading the bun installed in windows, not the bun I installed in WSL2. When I remove Bundows everything runs smoothly. — Reply to this email directly, view it on GitHub <#10281 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDVQCWDZGXIB6KPQVWT7URLY57LBZAVCNFSM6AAAAABGHS3QTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRUGAZTONRQHE . You are receiving this because you authored the thread.Message ID: _@**.**_>
Eu tenho Bun instalado em ambos os Windows e WSL2. Eu corro Bun no WSL2, não windows, mas eu recebo o mesmo erro que você, acho que é algum tipo de conflito entre as duas versões do Bun, tente remover um deles para ver se funciona.
If so, which versions of Bun would you uninstall? And which one would you keep?
I seem to have found the source of this issue. WSL for kali
Parece que encontrei a fonte desta questão. WSL para kali
Like this? Could you explain better?
@kauanlight it same with the error you got ..