Pengwin
Pengwin copied to clipboard
WhitewaterFoundry
rbenv and pyenv errors
Note
These WSL error messages occur from time to time and can tricky to troubleshoot short of reinstalling WSL.
They are usually not an issue with Pengwin itself but a glitch with the underlying Windows Subsystem for Linux in Windows 10.
You can help us help you and Microsoft improve WSL and address these if you can provide us some debugging information.
[x] I have read the above statement.
Basic Troubleshooting
Please check:
[x] I have confirmed WSL is enabled: https://docs.microsoft.com/en-us/windows/wsl/troubleshooting#confirm-wsl-is-enabled. [x] I have searched Google for the error message. [x] I have searched the official Microsoft WSL issues page: https://github.com/Microsoft/WSL/issues. [x] I have searched the Pengwin issues page: https://github.com/WhitewaterFoundry/Pengwin/issues. [x] I have reset Pengwin: Settings->Apps->Apps & features->Pengwin->Advanced Options->Reset. [x] I have disabled and re-enabled WSL in Windows Features. [x] I have run Windows 10 updates and restarted.
What other troubleshooting have you attempted to date?
Error Code
Insert here:
Please check:
[x] This error code is not one listed below.
Known Error Codes 0x80040306 Fix: https://docs.microsoft.com/en-us/windows/wsl/troubleshooting#error-0x80040306-on-installation 0x80040154 Fix: https://docs.microsoft.com/en-us/windows/wsl/troubleshooting#error-0x80040154-after-windows-update
Version
Find: Settings->Apps->Apps & features->Pengwin->Advanced Options->Version.
Insert here:
Screenshot
Windows Build
Run 'systeminfo | findstr /C:"OS"' in Command Prompt and insert here:
For help on retrieving: https://docs.microsoft.com/en-us/windows/wsl/troubleshooting#check-your-build-number
WSL Debug Data
Please collect and attach .etl files by following this guide: https://docs.microsoft.com/en-us/windows/wsl/troubleshooting#starting-bash-gives-an-error-code
We can certainly try.
Those look like line-ending clashes between CLRF and LRF and can happen sometimes when going back and forth between Linux and Windows.
Has that been explored at all?
This type of issue was once seen with git.
While looking into this issue, I found that pengwin-setup.d/ruby.sh file clones full git repository. Will it not be better if --depth=1 (i.e. shallow clone) is used? It can save a lot of space and time.
@spadino
Can you give us a step-by-step to reproduce these errors, so we can track them down?
Thank you.
Sure, it's pretty simple!
Fresh install of pengwin; mount windows drives in root; share home with windows user (/e/home/andrea, in my case); pengwin-setup; install ruby, python and node.
From my phone
From: Hayden [email protected] Sent: Monday, August 19, 2019 3:30:30 PM To: WhitewaterFoundry/Pengwin [email protected] Cc: Andrea Spada [email protected]; Mention [email protected] Subject: Re: [WhitewaterFoundry/Pengwin] rbenv and pyenv errors (#513)
@spadinohttps://github.com/spadino
Can you give us a step-by-step to reproduce these errors, so we can track them down?
Thank you.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/WhitewaterFoundry/Pengwin/issues/513?email_source=notifications&email_token=ABAY7O6SMQNOC6E5PQVERSDQFLRENA5CNFSM4IMKSHO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4T4IPA#issuecomment-522699836, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABAY7OYHQ7SSKP7RFJ2SWKDQFLRENANCNFSM4IMKSHOQ.
This happened to me when pyenv was installed for a user who's ${HOME} was within an NTFS windows handled disk. This seems to be the case for you @spadino as you state :
share home with windows user (/e/home/andrea, in my case)
No issue at all if install within the Linux filesystem. Indeed it was for me a CLRF and LRF issue as @sirredbeard mentioned above as pyenv was installing within the Windows filesystem with windows file endings, making it unstable within WSL. In order to retain data sharing between my WSL and Windows I opted for a /home/${USER}/${USER}_share directory to be shared with the Windows side rather than the whole /home/${USER} directory, as it also caused issues with other programs and config files stored in the users ${HOME} directory.
Hope this input helps.
