Lsp error in logs Unknown response id!

Nadie ha tomado este issue todavía.

Hi. I will appreciate any help.

Sometimes my server responds incorrectly. The server gives some responses eg.

```
{
_closeMessage = "Request cancelled.",
_closeReason = -32800,
id = 35,
jsonrpc = "2.0",
method = "textDocument/semanticTokens/range",
params = {
range = {
end = {
character = 0,
line = 0
},
start = {
character = 0,
line = 0
}
},
textDocument = {
uri = "---"
}
}
}
```

but the editor shows "workspace loading 0/0" or "Loading".

Even when it responds well, the same error appears in logs

```
[14:37:50.516][error][#0:script\proto\proto.lua:67]: Unknown response id! 0
stack traceback:
script\proto\proto.lua:67: in function 'proto.proto.response'
script\proto\proto.lua:195: in local 'f'
script\utility.lua:439: in metamethod 'close'
script\proto\proto.lua:202: in function
```

the difference is that when the server responds correctly, this appears in the logs:

`[09:40:35.887][info] [#0:script\provider\diagnostic.lua:557]: Diagnostics scope ...` (and here is my workspace folder)

however, when the server is working badly, the following appears in the logs:

`[14:37:50.619][info] [#0:script\workspace\workspace.lua:282]: Scan files at:` (and here are files from log/cache, not from my workspace I don.t know why.

Maybe someone faced such a problem?

Comienza reproduciendo la respuesta de LSP y comparando los logs alrededor de script/proto/proto.lua:67, script/proto/proto.lua:195 y script/workspace/workspace.lua:282. Rastrea por qué la respuesta recibe un ID desconocido y por qué el escaneo del workspace utiliza los archivos de caché registrados en los logs; se considera terminado cuando el fallo es reproducible y su causa y solución están verificadas.

Escrito por el modelo de indexación a partir del texto del issue.