-
Notifications
You must be signed in to change notification settings - Fork 665
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
Don't attempt to read baseline before it was generated #5961
Conversation
Sorry, mind running through what steps weren't happening before that are now? |
4.7.3 would write baseline, read it back and then use in |
@muglug this prevents a cosmetic issue where issues added to the baseline during current run are still reported: |
Thanks! Not sufficient for a separate release, but this is great. |
@weirdan This cosmetic issue is exactly what I was trying to achieve in #5838 after discussing it in #5831 :) When running with a baseline, it become impossible to know what issues have been added On our project, Psalm takes too long to run to hope adding it in CI, so we have a setup that runs Psalm regularly and saves the errors in baseline. Each time we see new errors, we handle them and report to whoever may be concerned. Without this, we need to run Psalm once without baseline, takes the issues and send them, then re-run Psalm with the baseline. Can we revert this change or introduce a new option to return to the described behaviour? |
Even with cache enabled? |
Trying to run Psalm without
😄
I don't remember the option we use, but we also retrieve in a file the whole list of issues reported by Psalm but the baseline is ignored when doing that so we retrieve every issue |
Fixes #5960
Previous fix would not return generated baseline.