File permission set wrong after pulling in with composer

[laravel]

File permission set wrong after pulling in with composer

[savaged]

I have upgraded from 5.3 to 5.4 on Homestead and am trying to use Dusk. I get the same issue: after running php artisan dusk the process runs until it times out.

[georaldc]

Mine was set to 0755 after upgrading from Laravel 5.3 to 5.4. I wonder if it's an OS issue (I have a centos setup through docker)

[brandonferens]

Perhaps. I initially had the issue on Dusk 1.0.3. Subsequent versions have been fine.

[thelfensdrfer]

I had to chmod the chromedriver-driver executable.

[browner12]

thanks for this. I can finally get Dusk to work! of course it had to be a permissions issue.

not sure how we fix this so composer updates don't revert it.

[thinsoldier]

Where is chromedriver-driver located?

[thelfensdrfer]

In the same path, vendor/laravel/dusk/bin/.

[AlexCW]

This worked for me, thanks! However only outside of homestead. In homestead the process just run indefinitely and does not run the tests.

[driesvints]

Heya. This might be something for the docs. Feel free to send in a PR there.