Fix incorrect timeout causing WSL1 OOBE to fail if the OOBE process takes longer than 30 seconds by OneBlue · Pull Request #13517 · microsoft/WSL
Summary of the Pull Request
If the OOBE process for a WSL1 distros takes more than 30 seconds, we'll hit the LAUNCH_PROCESS_DEFAULT_TIMEOUT_MS timeout which will cause the channel to be closed, which will fail the OOBE, causing all sorts of issues.
This change removes the timeout for this specific transaction, so we don't fail WSL1 OOBE if it takes more than 30 seconds to complete
PR Checklist
- Closes: Link to issue #xxx
- Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
- Tests: Added/updated if needed and all pass
- Localization: All end user facing strings can be localized
- Dev docs: Added/updated if needed
- Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx
Detailed Description of the Pull Request / Additional comments
This issue could cause OOBE failures looking like this:
λ wsl --install <distro> --version 1
Installing: <distro>
Distribution successfully installed. It can be launched via 'wsl.exe -d <distro>'
Launching <distro>...
Provisioning the new WSL instance <distro>
This might take a while...
<After 30 seconds>
<3>WSL (10 - SessionLeader) ERROR: SendMessage:131: Failed to write message LxInitOobeResult. Channel: OOBE
<3>WSL (10) ERROR: Broken pipe @src/shared/inc\SocketChannel.h:132 (SendMessage)
<3>WSL (10 - SessionLeader) ERROR: CreateProcessCommon:805: Create process failed