Christian Dietrich

hmmm 

no but it includes ``` { "ref": Object { "$refRef": b, "$error": "Could not resolve reference to NamedDotTargetReference named 'b'.", } } ``` but we dont care about `$error` (or...

possible fix: ``` if (restriction.label) { decoration.options.hoverMessage = {value: restriction.label}; } ```

workaround ideas: ``` override invalidateDocument(uri: URI): LangiumDocument | undefined { const result = super.invalidateDocument(uri) if (result !== undefined) { for (const node of AstUtils.streamAst(result.parseResult.value)) { AstUtils.streamReferences(node).forEach(refInfo => { const ref...

here is my attempts to reproduce the delete problem https://github.com/eclipse-langium/langium/compare/main...cdietrich:langium:cd-repro2 but with longer timeouts it works....

it looks like the delete problem might be a client side one. i dont always see all deletes arrive at the server.

created https://github.com/microsoft/vscode-languageserver-node/issues/1503 for the client side clarification

I see the problem also in normal mode when I change props eg to update text of Editor / switch model https://github.com/TypeFox/monaco-languageclient/discussions/858

@pisv @jonahgraham the the new commits on main this now fails in jenkins https://ci.eclipse.org/lsp4j/job/lsp4j-multi-build/job/main/172/console

i assume we need to do get in contact with foundation about secrets and do sth like https://github.com/eclipse-mwe/mwe/commit/a0a9a23630a949af92360e5d575d972ada02eb52#diff-230f39e46b3dd9ccd87ea11275922852fbe3543d18b8d4a41f8ad1304a1fcd32 unfortunately i have no capacity at all rn.