UnimplementedAbstractMethod on all enums when running PHAR version on Windows

[Shira-3749]

I've encountered an obscure bug when the .phar version of Psalm is run on Windows.

(This only happens with the .phar version. It works in both cases when installed via Composer.)

Psalm 5.22.2@d768d914152dbbf3486c36398802f74e80cfde48
PHP 8.3.3 (cli)

Given this psalm.xml:

<?xml version="1.0"?>
<psalm
    errorLevel="1"
    resolveFromConfigFile="true"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns="https://getpsalm.org/schema/config"
    xsi:schemaLocation="https://getpsalm.org/schema/config vendor/vimeo/psalm/config.xsd"
    findUnusedBaselineEntry="true"
    findUnusedCode="false"
>
    <projectFiles>
        <directory name="src" />
    </projectFiles>
</psalm>

And this simple enum definition in src/Example.php:

<?php

enum Foo {
    case A;
    case B;
}

When I run psalm.phar on the Windows host, I get the following output:

$ ./psalm.phar 
Target PHP version: 8.3 (inferred from current PHP version).
Scanning files...
Analyzing files...

ERROR: UnimplementedAbstractMethod - src/Example.php:3:6 - Method cases is not defined on class Foo, defined abstract in UnitEnum (see https://psalm.dev/101)
enum Foo {

------------------------------
1 errors found
------------------------------

Checks took 0.01 seconds and used 15.275MB of memory
No files analyzed
Psalm was unable to infer types in the codebase

But this passes when run inside a Docker container (based on php:8.3-apache).

root@d519a37baed3:/var/www/html/test/# ./psalm.phar 
Target PHP version: 8.3 (inferred from current PHP version).
Scanning files...
Analyzing files...

░
------------------------------
                              
       No errors found!       
                              
------------------------------

Checks took 1.17 seconds and used 30.963MB of memory
Psalm was unable to infer types in the codebase

[psalm-github-bot]

Hey @Shira-3749, can you reproduce the issue on https://psalm.dev? These will be used as phpunit tests when implementing the feature or fixing this bug.

[weirdan]

Reproduced: https://github.com/weirdan/10747

[weirdan]

The fun part is that the issue disappear when you extract the phar. Something tells me it's going to be fun to debug.