-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Fix #11797 crash on missing/renamed files #5921
Conversation
It's not finished yet. Should have marked it as draft |
I don't know.. I had a vague feeling we added something like this. But we do reproduce crashes with latest git head. |
@firewave sorry but I don't have the discussion in my head.. please feel free to comment on this.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nits..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
from my point of view I feel satisfied. @firewave please feel free to review..
This is okay as a catch-all to avoid the crashes (which is the most important in the short-term) but I still think it should be caught earlier. This needs a release notes entry. We also need Python tests for each project input which is lacking a file. I do not feel like adding tests later on which should have been there in the first place - again. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think test can be simplified.
firewave has made an effort to make sure tests can be executed from different folders. As your test is written I fear it must be executed from inside test/cli folder. |
Overall I think that it is a good strategy to fail immediately/early... But we should probably think more carefully about how we report problems. If we just report it directly in plain text on stdout/stderr then it is likely that cppcheck plugins will not accept it as expected output - the user might not get any information about what goes wrong. We also need to ensure that the problem is properly logged in the GUI. |
6d8c0aa
to
623cc0d
Compare
8b04daa
to
3119e09
Compare
ab841a0
to
34d7292
Compare
Crash was fixed with Simplecpp Fix and than bumped. |
No description provided.