Priority: P2: Important
Affects Version/s: Qt Creator 6.0.0-rc1, Qt Creator 7.0.0-beta1
Fix Version/s: Qt Creator 7.0.0-beta2
Commits:3cf6d15096 (qt-creator/qt-creator/7.0) 3cf6d15096 (qt-creator/qt-creator/master) 3cf6d15096 (qt-creator/tqtc-qt-creator/7.0) 3cf6d15096 (qt-creator/tqtc-qt-creator/master) 3cf6d15096 (qt-creator/tqtc-qt-creator/qds-3.1)
It happens rarely, but once in a while, one or more bogus diagnostics show up in the C++ editor when using the clang code model with clangd. They probably match a much older version of the file, and they definitely do not correspond to the latest diagnostics sent by the server. They must have been cached somewhere, but it's unclear where, and why they pop up all of a sudden. They even survive closing and re-opening the file.
Two examples are attached for illustration.
|For Gerrit Dashboard: QTCREATORBUG-26585|
|381920,2||ClangCodeModel: show specific client name in diagnostic||6.0||qt-creator/qt-creator||Status: MERGED||+2||0|
|385033,4||clangd: Assert on generating tooltip for deleted client||6.0||qt-creator/qt-creator||Status: MERGED||+2||0|
|390090,2||Clangd: clean up text marks after deleting client||master||qt-creator/qt-creator||Status: MERGED||+2||0|
|397327,5||LanguageClient: track all created diagnostic marks||7.0||qt-creator/qt-creator||Status: MERGED||+2||0|
|397753,3||ClangCodeModel: remove ClangdTextMark safety net||7.0||qt-creator/qt-creator||Status: MERGED||+2||0|