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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Internal Assertion Failure: Invalid cache key "\wsl.localhost" #10281

Closed
kauanlight opened this issue Apr 15, 2024 · 8 comments · Fixed by #11155
Closed

Internal Assertion Failure: Invalid cache key "\wsl.localhost" #10281

kauanlight opened this issue Apr 15, 2024 · 8 comments · Fixed by #11155
Assignees
Labels
bug Something isn't working windows An issue that only occurs on Windows

Comments

@kauanlight
Copy link

kauanlight commented Apr 15, 2024

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())

@kauanlight kauanlight added the bug Something isn't working label Apr 15, 2024
@Electroid Electroid added the windows An issue that only occurs on Windows label Apr 15, 2024
@aiktb
Copy link

aiktb commented Apr 18, 2024

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.

@aiktb
Copy link

aiktb commented Apr 18, 2024

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.

@kauanlight
Copy link
Author

kauanlight commented Apr 18, 2024 via email

@aiktb
Copy link

aiktb commented Apr 18, 2024

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.

@kauanlight
Copy link
Author

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?

@Ayo-J
Copy link

Ayo-J commented Apr 20, 2024

I seem to have found the source of this issue. WSL for kali

@kauanlight
Copy link
Author

Parece que encontrei a fonte desta questão. WSL para kali

Like this? Could you explain better?

@Ayo-J
Copy link

Ayo-J commented Apr 22, 2024

@kauanlight it same with the error you got ..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working windows An issue that only occurs on Windows
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants