Internal error while analysing file (but no details about what the error actually IS) #10509
Comments
|
Hi, is the code PHPStan crashes on public? Can you point me to a series of bash commands I should run to get this reproduced locally? Starting with |
|
They are public, I listed them in the main issue:
There's also a link in the issue to a reproduction of the error on phpstan.org I'm about to go to bed but I'll try to remember to give a full set of bash commands tomorrow, if you haven't managed to reproduce with this information by then 👍 |
Please do, the repository doesn't have a PHPStan config so I have no idea how to reproduce it. |
|
Oh the playground actually shows it, never mind :) Will take it from here. |
|
Oh so this is a definitely weird type: |
|
Alright, avoiding the internal error: phpstan/phpstan-src@778b569 As for the actual feature, I have no idea if the type is legit and how should PHPStan support it, or of it's misunderstood by the developer who wrote the code, and they should do something else. Better open a new feature request and describe it 👍 Thanks. |
|
Thank you for sorting that out so quickly. |
|
If you check the typical release cadence https://github.com/phpstan/phpstan/releases you can deduce it's not too far off :) |
|
Thanks. There's no way for me to know if that pattern is intentional or a fluke so I'll take that comment as confirmation that it's intentional. 👍 |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Bug report
I ran
vendor/bin/phpstanand it gave me some error output, including a message to "Run PHPStan with -v option and post the stack trace".As requested the full verbose output with stack traces is below.
Click to see verbose console output
I've ommitted the successful output and just started from the error.
I can't give the full output because when I try to, GitHub says "There was an error creating your Issue: body is too long (maximum is 65536 characters)."
Instead I have included the output for the first two classes mentioned, with the (hopefully correct) assumption that all four errors are the same.
The source files for the named files are:
Code snippet that reproduces the problem
https://phpstan.org/r/69735775-ef2c-49a6-bc88-74ebed02734d
Expected output
Instead of an error, the file should be checked against the rules we're using and normal PHPStan errors outputted for those specific rules where applicable.
Did PHPStan help you today? Did it make you happy in any way?
No response
The text was updated successfully, but these errors were encountered: