(Windows) EH Plugin randomly stops retrieving metadata starting with v.0.8.5 #622
-
Beta Was this translation helpful? Give feedback.
Replies: 10 comments
-
Can you try switching to WSL2 and see if the issue persists? I believe the issue is caused by WSL1 not liking the update to alpine 3.14 as the base for the linux distro. |
Beta Was this translation helpful? Give feedback.
-
Tried again after switching to WSL2, same issue **Log files**Making sure the WSL distro is using specified WSL mode: 2. C o n v e r s i o n i n p r o g r e s s , t h i s m a y t a k e a f e w m i n u t e s . . . |
Beta Was this translation helpful? Give feedback.
-
Looking at the first lines of the log, it appears your windows install doesn't have virtualization support enabled, so the switch to WSL2 didn't work. (admittedly I should provide better error messaging for this case) See https://docs.microsoft.com/en-us/windows/wsl/install-manual#step-3---enable-virtual-machine-feature |
Beta Was this translation helpful? Give feedback.
-
Did that, same, but I think I figured out what is breaking it. **Log files**Making sure the WSL distro is using specified WSL mode: 2. C o n v e r s i o n i n p r o g r e s s , t h i s m a y t a k e a f e w m i n u t e s . . . Let me know if there is something else that I can try. |
Beta Was this translation helpful? Give feedback.
-
Looks to still be in WSL1 mode -- You can check whether it's on 2 or not with the command Do you have virtualization enabled in BIOS? |
Beta Was this translation helpful? Give feedback.
-
You're right, seem to be still running in wsl1 mode, even with virtualization enabled and the wsl2 switch on the settings. I tried to convert it via command line but appears to fail the conversion and if I set the default installation to wsl2 then the installer will fail when it has to deploy the distro (4b29353) |
Beta Was this translation helpful? Give feedback.
-
well, after fiddling with every setting under the sun it appears my machine can't run anything using wsl2 (Ubuntu also fails to install if the default is set to wsl2)
anyway, just gonna run the last nightly that I have around that didn't had this issue under wsl1, thanks for your help. |
Beta Was this translation helpful? Give feedback.
-
Just thought I would leave this here: microsoft/WSL#6376 |
Beta Was this translation helpful? Give feedback.
-
yeah, I assumed it was something like that, good to see a confirmation. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the details! As mentioned in the other issue about this problem:
WSL1 will remain an option since some setups can't move to 2 (unsupported CPUs and LTSC windows installs), but I can't realistically keep holding the stack back for those. 😓 The Alpine update was already a bit overdue... I'll be converting this issue to a discussion so others can find it easily, as it already has quite a bit of information. ☝️ |
Beta Was this translation helpful? Give feedback.
Can you try switching to WSL2 and see if the issue persists?
I believe the issue is caused by WSL1 not liking the update to alpine 3.14 as the base for the linux distro.