https://linen.dev logo
Powered by
b
Hello 👋, We are trying to setup Mirrord using WSL with Ubuntu to run a Rider project. The plug-in seems to not work when trying to launch the application with Debug and we observed the following behavior : 1. Clicking on "Select Active config does nothing" 2. Click on "Settings" open a mirrord.json that does not seems to be inside the project .mirrord/json that seems to be under Windows file system on a weird location (see screenshot). Message.txt contains attached Rider logs with a stack trace for : Index is not created for 
mirrordConfig
Any idea ? Thanks in advance ! https://cdn.discordapp.com/attachments/950020257156833340/1466467437594546308/message.txt?ex=697cd9ba&is=697b883a&hm=0da207c0194da16c8229a53aa5085f30f55103dfae7c5f261e71946e916774cd& https://cdn.discordapp.com/attachments/950020257156833340/1466467438106378280/image.png?ex=697cd9ba&is=697b883a&hm=5ebe3987357012e439f5d43be11d98238bff9b85c2b833d8dd9a47dd96426c68&
a
Hey, You need to install the IDE plugin both on host and backend. It’s confusing but go to IDE settings you’ll see that plugins appears twice. Make sure you install in both
b
Hey ! It was the case, we tried to run the Rider inside WSL is that a supported scenario ?
I mean, with that this is supposed to be two separate IDE no ?
One on the windows fs and one on ubuntu ?
a
That specific error sounds like it’s running on windows but using WSL
b
The plugin ?
Behave like it was on windows even if it's running inside WSL right ?
a
it should work - justn eed to install the plugin on both sides.
Go to IDE settings -> Search "Plugins"
You should see two entries - install in both mirrord.
b
> install in both mirrord Not sure to understand this correctly. We are expecting mirrord plugin installed two times here right ?
a
yes
b
And to be sure that we are not doing anything wrong, this is using the "Remote development" feature of Rider that download and install another Rider instance in the WSL right ?
Also, do we need to share project file ? It's recommended on the documentation to avoid using 
/mnt
inside WSL but rather having another copy in the WSL filesystem to work on the project for performance reason
a
yes, you're rigt
b
I'll indicate my team to retry tomorrow knowing that specific setup to see how it's going
Thx for details 🙏 ! Keep you posted on that
a
feel free to schedule time with us to help you setup if you'd like.
b
@Aviram Hassan we had time to test with team. Thx for the "install in both mirrord" it was what we missed 👍
By any chance, do you ever experienced filesystem errors while trying to debug a statefulset ? We have a single replicat of this statefulset and we have such stacktrace in our .NET App :
Copy code
DirectoryNotFoundException: Could not find a part of the path '<CUSTOM_PATH>'.
   at Interop.ThrowExceptionForIoErrno(ErrorInfo errorInfo, String path, Boolean isDirError)
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String path, OpenFlags flags, Int32 mode, Boolean failForSymlink, Boolean& wasSymlink, Func`4 createOpenException)
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, UnixFileMode openPermissions, Int64& fileLength, UnixFileMode& filePermissions, Boolean failForSymlink, Boolean& wasSymlink, Func`4 createOpenException)
   at System.IO.Strategies.OSFileStreamStrategy..ctor(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable`1 unixCreateMode)
   at System.IO.File.Create(String path)
We used 
write
mode in the config, also this code is really legacy tbh 😂
a
what's the path? perhaps it needs to be set in 
feature.fs.write
paths?
also are you running native or WSL?
it seems native 👀
b
The path is :
Copy code
/var/opt/datagalaxy/WebServer/meta/Log/2026_02_03@12_22_08/R_2026_02_03_0000/00000002__api_filtered-views_OUT.jsonDetails
This is a legacy request logger to file that is really old. On the 
feature.fs.write
we have to specify path where we can write to ? It was on WSL, indeed the stacktrace is using Windows API and that is really weird tbh
a
might be that /var/opt is default local, I don't remember
I'd put it to be explicitly
btw I think you might prefer 
feature.fs.mapping
feature
so it'll just write the logs locally
b
instead of writting in the cluster, write the debug session in local path to have it on my computer right ?
a
y
b
ok thanks for sharing this, we will try !
keep you posted 🙏
7 Views
PreviousNext
Powered by