-
Notifications
You must be signed in to change notification settings - Fork 672
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
Clear cache after composer.lock change #3155
Comments
Hey @greg0ire, can you reproduce the issue on https://psalm.dev ? |
Nope, sorry little bot |
I think this was fixed in the current release - do you still see it? |
@muglug |
Try with |
It must have to do with cache because it works after a reboot. |
@greg0ire Then, I believe, you can close the ticket. 😉 |
I will let Matthew Brown decide on this, maybe there is something that needs to be fixed, like auto-cleaning the cache under some circumstances. Or maybe this will never happen again for some other reason and it can be closed, but since it happen to me and other people, I guess it could happen again to anyone. |
@zerkms this fits the bill of an easy problem to fix – the cache should clear whenever there's a lockfile change, but it appears not to be |
However multiple lockfiles may need to be considered when Psalm is installed globally (with |
Note that upgrading to v4.4.0 fixes the issue
The text was updated successfully, but these errors were encountered: