New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mixing up classes in some tests #8357
Comments
Hey @DanielBadura, can you reproduce the issue on https://psalm.dev ? |
@someniatko re #8249, care to take a look? Just from skimming through it I think this is a separate case from #8257. |
@AndrolGenhald isn't #8335 supposed to fix the regression? |
@someniatko Sorry, forgot about that one, @DanielBadura could you test with |
IMO 4.25.1 should be released with the regression fix, because it's already the second encounter of the issue. |
Agreed, I've got no idea how to do releases though so I'll just let @orklah handle it 🙂 |
p.s. if our suggestion is correct, it should be a duplicate of #8330 |
Can confirm that no issue occur with |
Released as 4.26.0 :) |
Our CI build failed for auto upgrading our dependencies. In there psalm was updated from 4.24.0 to 4.25.0. Psalm now reports some strange errors like:
Assuming that
$profile
is an instance ofAggregateRootTest
but it is instead an instance ofAggregateRoot
. See here for the code: https://github.com/patchlevel/event-sourcing/blob/2.1.x/tests/Unit/Aggregate/AggregateRootTest.php#L54-L58Also here the full error list from our workflow: https://github.com/patchlevel/event-sourcing/runs/7616545968?check_suite_focus=true
Since the dependency update PR did update multiple deps, i tried it locally with only updating psalm with the same result.
I'm not sure whats going on if this is something on our side or broke with the new release. All errors are located in the tests folder and also only a tiny bit of these tests are affected.
The text was updated successfully, but these errors were encountered: