While developing the Visual Studio Code extension, I have noticed that broken link diagnostics for links to generated atom feeds (like /foo/atom.xml) are published, but then appear to be retracted once something happens. (Sorry for the vagueness).
Any idea what might be going on here? I can also publish the code of the VS Code extension if that helps.
In order to improve responsiveness I have made it so that the initial build runs in the background and resolves a promise once it completes. I thought that all diagnostics would wait for this to happen, but it seems the link errors are slipping through. It's good that the error disappears once the build resolves though.