Files that match ignoreGlobs are not included when workspace diagnostics are run again

[Tazmondo]

If a file matches your ignoreGlobs setting, then it seems not to be included when workspace diagnostics runs, and so you have to open the file for its type signature (not sure if this is the correct word, just the shape that requiring it returns, what functions it has etc) to update when it is changed by some external source.

For context:
I am using Blink for my networking, and it auto-generates luau files with events in them. I have these ignored because they have warnings. When Blink runs, I have to open the file before requiring them gives the correct results. I should not have to open the file, since I have workspace diagnostics on.

If I remove these files from my ignoreGlobs then everything works as expected (but I now have to deal with warnings that I can't fix)

[Tazmondo]

After a bit more experimentation:

The behaviour is very inconsistent and I'm not exactly sure what's going on? It feels like there's something where, if I have opened the generated file at least once, even if it's now closed, then everything works as expected. I've also noticed when this happens the diagnostics for the files are still reported, even though they shouldn't be because the file has been closed and they've been ignored. Might be worth making a separate issue for that.

for example, when it's not working:

We have a file A that gets edited by an external program
file B requires A

neither B nor A are open
A is replaced with a new file by an external program
B should now get a type error (when workspace diagnostics are run again, I'm aware doing this in response to the external program is another can of worms) because something inside A has changed
neither B nor A get errors until either one is opened (sometimes you have to open A for any type errors to occur in B, and sometimes even after opening A you then have to also open B to get errors? might be related to the thing I said above where opening the file at least once causes it to work)

To trigger workspace diagnostics to run again, I'm working in an unrelated file C. I'm under the impression this should recompute for every file but is it only files that relate to C?

Also if I just reload the language server, the diagnostics are computed accurately.

I wish I could better describe the problem for you but it's hard to track down exactly what's going on