-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[5.x] Fixes issue if there is no herd
or valet
installed
#343
[5.x] Fixes issue if there is no herd
or valet
installed
#343
Conversation
656e86e
to
466a710
Compare
@Anticom can you check if this PR solved it? Thanks. |
herd
or valet
installed.herd
or valet
installed
I'm getting promted for a password now multiple times? Is this normal in 5.x branch of installer? First was after setting app key:
second time after:
All I did to check out your MR was cloning your fork into ~/.composer/vendor/laravel/installer and checking out your branch. |
Nice! the password prompts does not seem related with this. Thanks for checking it out. |
Yeah I figured it probably has nothing to do with the changes you made to fix the issue. I'll keep you posted once the fix is released. @xiCO2k |
herd
or valet
installedherd
or valet
installed
Would love if this could be pushed to a new version 5.8.2, this currently breaks the Laravel installer entirely on WSL2 :/ |
I just published a new release for this one. |
I updated using composer and am still getting promted for password. |
Ok but that worked without any error? |
I think my original reply was worded incorrectly , what I had meant was that this PR did solve #342 and that it should be merged as the issue described in #342 currently causes the installer on WSL2 to not work at all |
@rjindael can you create an issue with the error you are getting? Thanks. |
Sorry, I think I was not clear, I am not experiencing any issues now, only previously did before this PR was merged. 🙂 |
@rjindael So you're not getting promted for passwords during execution of |
No |
This PR fixes the issue #342.
I could not replicate on my machine but based on the error information provided by @Anticom, catching the
ProcessStartFailedException
it should solve.Cheers.