InvalidArgument error introduced in 5.24 about psalm HOT 6 OPEN

I did check for any stubs used, but in the whole project there is no stub for TwigFilter class. I do use psalm/plugin-symfony v 5.1.0, but this stub is not there. So Id assume it reads signature from the source code (vendor/twig/twig/src/TwigFilter.php)

from psalm.

Also please note that this syntax is in line with official Symfony docs for Lazy loaded twig extensions

from psalm.

This error is showing up on more places now. E.g. in the Syfony\Console\Command\Command::setCode() function.

ERROR: InvalidArgument - src/Command/AbstractEndlessCommand.php:55:25 - Argument 1 of Symfony\Component\Console\Command\Command::setCode expects a public callable, but a non-public callable provided (see https://psalm.dev/004)
        parent::setCode([$this, 'runloop']);

when I use protected modifier for function runloop. I repeat, there is no psalm param specification requiring that the callable should be public, nonstatic or whatever. Only callable. And I am unable to reproduce this on psalm.dev - https://psalm.dev/r/3c405968f1

Version 5.23 works just fine

from psalm.

I found these snippets:

<?php

class Command{
    /**
     * @param callable $code
     */
	public function setCode(callable $code): static
    {
        return $this;
    }
}

class Code extends Command{
    public function __construct(){
        parent::setCode([$this, 'runCode']);
    }
    
    protected function runCode(): void
    {}
}

Psalm output (using commit 16b24bd):

No issues!

from psalm.

Aha, the reason why I cannot reproduce this issue on psalm.dev is because it uses this version:

https://github.com/vimeo/psalm/blob/16b24bdc94e052b5ce69fd232a77416a1f6ec3e6/src/Psalm/Internal/Analyzer/Statements/Expression/Call/ArgumentAnalyzer.php

Which does not contain the breaking PR #10839

@weirdan can you please look into this, as you reviewed the change and also it seems you are in charge of merging code into master branch, which is what psalm.dev uses?

from psalm.

You can close the issue because it's already fixed in #10935.

Just wait for a new release.

from psalm.