-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Problem saving / opening collections in WSL2 #159
Comments
@binaryfire Glad that you like Bruno ! Need some help to debug this issue. When a To debug, first you can toggle dev tools (Click on This should help us narrow down the issue on whether the event fire by electron reaches the UI or not. |
I'm also experiencing this. In fact, even if I move a working Bruno folder to WSL2 and then open the collection from there, Bruno only shows me the collection name and the folders under it, but no requests at all. I tried the above steps, enabling dev tools and running When removing the collection and re-adding it, there are two Please let me know how I can help debug this further! Please note that I have my WSL2 mapped as a network drive, but the same issues happen when using a collection on the Edit: I have more info: When running Bruno.exe from the command line, I was able to see the errors. Pasting them below: Paste from Command Line
|
I just ran into this same issue. Decided to dig into the source a little and found this... The issue appears to be a result of using fs.watch which isn't recommended for network paths (and WSL is accessed via network path). A simple workaround is to set the environment variable A more permanent fix could be conditionally setting the polling mode based on the path type. In watcher.js:415 the parameter |
Alternatively, if you validate the prerequisites for running GUI apps from WSL2, you can run bruno as GUI from the WSL itself and it seems to just work fine. |
Yep, installing Bruno in WSL directly (I used apt) worked for me, thanks! |
Came here to say WSL paths do not work. Glad I'm not the only one. Hopefully one day bruno will support this. |
@binaryfire @eblount @nicklargent @SpiRanha @GimpMaster This has been fixed in @gyunseo Many thanks for the PR! |
Hey @helloanoop. Only had time to do a quick test but so far so good! I'll let you know if I have any other problems. |
@helloanoop I don't see any change here, sorry:
|
1.5.1 worked just fine for me. Basically clicked create new collection. Choose \wsl$.localhost\Ubuntu\tmp\bruno Created a request and it showed up. Thanks @helloanoop |
Okay, using the |
Works over here too, thanks! No more workaround. |
Is anyone else having problems renaming folders on WSL2? It'd be great if someone could test this and let me know - I'm not sure if it's a bug or if it's something to do with my system. To reproduce: right click on a folder inside a collection, click "Rename" and try and change the name to something else. The name doesn't change. |
I've opened a new issue here: #1302 Looks like there are issues with several file operations in WSL2 |
Hi. Great project!
I'm using Windows 11 + WSL2. I've installed the client in Windows and have specified the collection location as
\\wsl.localhost\Ubuntu-22.04\home\myhomedir\mycollection
. Thebruno.json
file is created correctly and requests are saved as.bru
files but they don't appear in the UI. I'm guessing the format of the path is messing something up.What is the recommended way of using Bruno with WSL2?
Cheers
The text was updated successfully, but these errors were encountered: