Gary Guo
Gary Guo
No that works with Hyper-V VM but not WSL. Did you launch wsldhost with admin privilege?
Can you try ```toml [x11] display = 0 force = true ``` in your config? WSL doesn't clean `/tmp`, so sometimes WSLD will have issue creating the socket...
One approach would be to mount `/tmp` with tmpfs in your fstab.
@isaac84 does the `force=true` workaround above not work for you?
That approach will cause all your X connections to drop when you resume from sleep, or when network status changes (the reason that I created wsld in the first place).
The privilege in wsl (and thus wsld) is pretty complicated. Vsock connection must be made from the user who starts wsl, and `hcsdiag` (or the equivalent API used in wsld)...
Passing CI: https://github.com/lowRISC/opentitan/actions/runs/10998725968/job/30537297981?pr=24605
> `rust-toolchain{,.toml}` files can [cause arbitrary code execution](https://github.com/rust-lang/rustup/issues/2879), and IDEs are looking to [_disable_ toolchain file support](https://github.com/rust-lang/rustup/issues/2793). In that context I don't think a hidden file is a good idea....
Turns out I can't use the ci-admins team because it doesn't have write access to this repo. Marking as draft now.
> Hi @nbdd0121! Is this stale or is there anything that makes sense to do with it? Unfortunately this doesn't work as `ci-admins` team does not have write access to...