Indexer not running for new CMake projects after build

[jonahgraham]

There seems to be a race condition when doing a build of the project. Steps to reproduce:

1. File -> New -> C/C++ Project -> CMake
2. Enter project name and press Finish

You end up with (sort of as expected because there is no compile_command.json yet) errors in the editor:

Doing an initial build of the project leads to improvement, but the indexer isn't being triggered (as you can see from the unresolved includes):

Doing a re-resolve unresolved includes solves the problem:

The above screenshots captured with Eclipse C/C++ EPP for 2023-03 on Linux.

[jonahgraham]

Is there a race condition or a missing step in the code here where the indexer should be re-run once the compile commands json is read/re-read?

[15knots]

If you close the file and re-open it, looks the file like having been indexed then? Or if you switch to a different editor tab and back then?

In my MBS-cmake plugin, it turned out I have to explicitly tell the indexer to refresh for opened files.

CDT does not seem to trigger re-indexing.