UNC paths as argument throws error

[Francismori7]

• Pint Version: 0.2.1
• PHP Version: 8.0.13 (locally installed on Windows)

Description:

I'm using WSL2 with Sail. At this point, I'm trying to use PHPStorm to automatically run Pint on the current PHP file, which works correctly when I'm on a local path.

The issue comes when you open a project from the WSL UNC path (network share). For instance, my project is located at \\WSL$\UBUNTU\home\morfra\code\XXX

Here is the full error when running the following command:

cmd.exe /D /C call C:\Users\morfra\AppData\Roaming\Composer\vendor\bin\pint.bat \\wsl$\Ubuntu\home\morfra\code\XXX\app\Http\Middleware\RecordPageViewsToActivityLog.php
'\\wsl$\Ubuntu\home\morfra\code\XXX'

In Runner.php line 242:
                                                                                                                       
  Cannot write to file "\\WSL$\UBUNTU\home\morfra\code\refonte-intranet\app\Http\Middleware\RecordPageViewsToActivity  
  Log.php" as it is not writable.

That being said, Windows specifically says "UNC paths are not supported in CMD", but I've never had any issues with other scripts running like that.

Steps To Reproduce:

Run the pint.bat command from Windows against a UNC path:
pint.bat "\\wsl$\Ubuntu\home\morfra\code\XXX\app\Http\Middleware\RecordPageViewsToActivityLog.php"

[driesvints]

Please include the issue template when submitting issues

[Francismori7]

Please include the issue template when submitting issues

How was I able to submit an issue without the template? :-/ I swear it wasn't there..!

[driesvints]

What path did you take to submit it?

[Francismori7]

What path did you take to submit it?

It was the regular New Issue button on the issues page, which is why I'm surprised.
I went ahead and changed my original issue with the template.

[driesvints]

This is what I see when I choose a bug report. Did you misclick on feature request?

[nunomaduro]

@Francismori7 Sorry, but I am familiar with the contents you described in the pull request. Of course, you can always submit a pull request that helps fixing your issue.

[michalkortas]

@Francismori7 hey, in this situation I have a little workaroud.

Instead running pint.bat from Windows disc directly use your WSL2 Linux console & run pint from mounted Windows disc, just like that:

[Francismori7]

@michalkortas Thanks. That's what I resorted to be doing. However this poses a problem when using it through PHPStorm as a file watcher, it's not something I can configure easily

[plakhin]

@Francismori7 not sure if this helps, but once I faced similar issue with running Pest from Sublime Text under WSL2, I've used this command wsl.exe --cd "/home/stan/www/laravel-test" vendor/bin/sail artisan test --filter ExampleTest that you can adapt and try something like this: wsl.exe --cd "/home/morfra/code/XXX" vendor/bin/pint app/Http/Middleware/RecordPageViewsToActivityLog.php

[Francismori7]

@Francismori7 not sure if this helps, but once I faced similar issue with running Pest from Sublime Text under WSL2, I've used this command wsl.exe --cd "/home/stan/www/laravel-test" vendor/bin/sail artisan test --filter ExampleTest that you can adapt and try something like this: wsl.exe --cd "/home/morfra/code/XXX" vendor/bin/pint app/Http/Middleware/RecordPageViewsToActivityLog.php

This worked very nicely. Thanks for the help!