Avoid mass extraneous clang linting errors
-
On occasion, a project can fall to a state where clang incorrectly lints the code and begins tagging issues everywhere. This is best identified by core objects we know are sane being marked up.
I believe this to be cache files with timestamp changes may be getting rejected. Any changes outside of the toolset after the caches were made seem to cause this. Restarting usually fixes this, but just so people know, I'll post this here anyway.
If anyone knows what can cause this, it would be very helpful. I think I've narrowed it down to not changing project files outside, but I am not completely sure about that as I haven't had any way to confirm it. It does happen occasionally at other seemingly random times, so this makes me wonder if some other issue is at play.
Any information would be helpful. Anyone with similar problem, just restart the program. If you recently had time zone changes or issues with the system clock (this is rare these days) you may wish to touch all your project files outside before starting again.
-
C Christian Ehrlicher moved this topic from General and Desktop on
