Annotation warnings are bleeding over from other workspaces

How are you using the lua-language-server?

Visual Studio Code Extension (sumneko.lua)

Which OS are you using?

Windows

What is the issue affecting?

Annotations, Diagnostics/Syntax Checking

Expected Behaviour

Annotation warning from another workspace do not show up in the current workspace.

Actual Behaviour

Workspace structure is as follows

\Projects
  -- Annotations (separate workspace, VS Code has setting "Lua.workspace.library" referencing this folder)
  -- Project 1 (separate workspace)

Annotations are over 100 files defining the API surface of a hosting program. In the workspace for the annotations, the diagnostic for missing-return is turned off for that workspace. This is to allow for the annotation of methods on the API via function nomenclature. Naturally, these functions do not have any implementation and the diagnostic warning appears.

When the annotations are referenced (---@type) in another project workspace (e.g., Project 1 above), these diagnostic warnings can appear in the workspace for Project 1. Clicking the warning in the Problems area to open the file and then closing the file dismisses the warnings for that file.

Reproduction steps

There are no specific "steps" to recreate this problem.

Additional Notes

No response

Log File

file_e%3A_Games_RedGuides_MacroQuest_lua_FightForge.zip

Inizia ispezionando il log allegato e riproduci il layout descritto con un Annotations workspace referenziato tramite Lua.workspace.library e un workspace separato Project 1. Traccia il motivo per cui le diagnostiche sui valori di ritorno mancanti oltrepassano il confine del workspace; il lavoro è completato quando gli avvisi disabilitati nell’Annotations workspace non compaiono in Project 1, senza richiedere che il file venga aperto e chiuso.