DefaultLinker.createLinkingError trap for document phases

[cdietrich]

Hi,

in a big workspace we run into this

at DefaultLinker.createLinkingError (/Users/dietrich/.vscode/extensions/everestsystems.lotse-language-vscode-0.4.4/out/language-server/main.cjs:119629:36)
    at DefaultLinker.getCandidate (/Users/dietrich/.vscode/extensions/everestsystems.lotse-language-vscode-0.4.4/out/language-server/main.cjs:119494:32)
    at DefaultLinker.doLink (/Users/dietrich/.vscode/extensions/everestsystems.lotse-language-vscode-0.4.4/out/language-server/main.cjs:119436:34)
    at /Users/dietrich/.vscode/extensions/everestsystems.lotse-language-vscode-0.4.4/out/language-server/main.cjs:119428:52
    at _StreamImpl.forEach (/Users/dietrich/.vscode/extensions/everestsystems.lotse-language-vscode-0.4.4/out/language-server/main.cjs:102971:7)
    at DefaultLinker.link (/Users/dietrich/.vscode/extensions/everestsystems.lotse-language-vscode-0.4.4/out/language-server/main.cjs:119428:30)
    at runNextTicks (node:internal/process/task_queues:65:5)
    at process.processImmediate (node:internal/timers:453:9)
    at process.callbackTrampoline (node:internal/async_hooks:130:17)
    at async LotseDocumentBuilder.runCancelable (/Users/dietrich/.vscode/extensions/everestsystems.lotse-language-vscode-0.4.4/out/language-server/main.cjs:122692:9)
    at async LotseDocumentBuilder.buildDocuments (/Users/dietrich/.vscode/extensions/everestsystems.lotse-language-vscode-0.4.4/out/language-server/main.cjs:122645:5)
    at async LotseDocumentBuilder.update (/Users/dietrich/.vscode/extensions/everestsystems.lotse-language-vscode-0.4.4/out/language-server/main.cjs:122518:5)
    at async LotseDocumentBuilder.update (/Users/dietrich/.vscode/extensions/everestsystems.lotse-language-vscode-0.4.4/out/language-server/main.cjs:142247:7)
    at async /Users/dietrich/.vscode/extensions/everestsystems.lotse-language-vscode-0.4.4/out/language-server/main.cjs:122937:24
    at async Promise.all (index 0)
    at async DefaultWorkspaceLock.performNextOperation (/Users/dietrich/.vscode/extensions/everestsystems.lotse-language-vscode-0.4.4/out/language-server/main.cjs:122935:5)

the stacktrace is at the
Attempted reference resolution before document reached ComputedScopes state

do you have an idea how this can happen? to me it looks like we are in the update call
so how can this ever happen?
do we have a problem that document states are reset before the current task is cancelled?

[msujew]

Hey @cdietrich,

Hm, I'm not too sure either. Do you have a reproducible example? Since we did a lot of work on the document builder and workspace lock, I haven't seen this error anymore.

[cdietrich]

No I also could not reproduce yet again with more logging