Execution on Windows

[abrahamsaanchez]

Bug Report

Subject	Details
Rector version	1.2.8

I follow the installation guide on https://getrector.com/documentation but I cant execute rector.

$ composer require rector/rector --dev
./composer.json has been updated
Running composer update rector/rector
Loading composer repositories with package information
Updating dependencies
Lock file operations: 2 installs, 0 updates, 0 removals
  - Locking phpstan/phpstan (1.12.7)
  - Locking rector/rector (1.2.8)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 2 installs, 0 updates, 0 removals
INFORMACIÓN: no se pudo encontrar ningún archivo para los patrones dados.
  - Installing phpstan/phpstan (1.12.7): Extracting archive
  - Installing rector/rector (1.2.8): Extracting archive
Generating autoload files
68 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
No security vulnerability advisories found.
Using version ^1.2 for rector/rector

$ vendor/bin/rector
El sistema no puede encontrar la ruta especificada.

Don't know if it's a Windows issue, but the error is saying "The system cannot find the path specified." (my OS is in Spanish).

[samsonasik]

define paths, read the documentation https://getrector.com/documentation/define-paths

[abrahamsaanchez]

define paths, read the documentation https://getrector.com/documentation/define-paths

Rector is not even configured (the rector.php file is not created and it should be created by rector automatically).

Even if I create the rector.php configuration file, doesn't work:

<?php

use Rector\Config\RectorConfig;

// Also tried with ->withPaths([ __DIR__ . '/src'])
return RectorConfig::configure()
    ->withRootFiles();

$ vendor/bin/rector
El sistema no puede encontrar la ruta especificada.

[samsonasik]

I can't reproduce, ensure you're using prompt or bash, per documentation known drawback https://github.com/rectorphp/rector?tab=readme-ov-file#known-drawbacks

[abrahamsaanchez]

I tried with Bash, prompt and PowerShell and the error is the same.

The process die with the error message on the Application class, when the doRun method is called.

Don't know if this can help, but I made changes to the Application file to see when the process dies:

run method

print_r('before doRun');
exit;
$exitCode = $this->doRun($input, $output);

$ vendor/bin/rector
before doRun

$exitCode = $this->doRun($input, $output);
print_r('after doRun');
exit;

$ vendor/bin/rector
El sistema no puede encontrar la ruta especificada.

doRun method

public function doRun(InputInterface $input, OutputInterface $output)
{
    print_r('inside doRun');
    exit;

$ vendor/bin/rector
El sistema no puede encontrar la ruta especificada.

[samsonasik]

we may need github repo with reproducible example, eg: via github action :)

[nschilling]

I had a similar problem on Windows 11. I disabled xdebug in the php.ini to make rector work.

When xdebug is enabled the handler \RectorPrefix202409\Composer\XdebugHandler\XdebugHandler tries to restart rector without xdebug.
Unfortunately it produces an invalid command on windows. It is similar to this:

"C:\path with spaces\php.exe" "-n" "-c" "C:\Users\path with spaces\AppData\Local\Temp\1234.tmp" ".\bin\rector"

In PowerShell it needs to prepend an ampersand, I think;

& "C:\path with spaces\php.exe" "-n" "-c" "C:\Users\path with spaces\AppData\Local\Temp\1234.tmp" ".\bin\rector"

[samsonasik]

The effort to cover windows with spaced path and enable parallel was on PR:

• [Parallel] Handle Spaced root project main script on parallel process rector-src#4813

on WorkerCommandLineFactory which works on bash and prompt, feel free to provide better patch that support powershell as well.

[staabm]

When xdebug is enabled the handler \RectorPrefix202409\Composer\XdebugHandler\XdebugHandler tries to restart rector without xdebug.
Unfortunately it produces an invalid command on windows.

If reproducible in isolation this should be reported to the xdebug-handler repo

[github-actions]

This issue has been automatically locked because it has been closed for 150 days. Please open a new issue if you have a similar problem.