Rafał Chłodnicki

I think it's fine to close this now since that specific error won't happen anymore. There were various fixes that improved the situation - caching of the tokens, some extra...

Creating `CompletionItem` with just a "trigger" seems to make no significant difference to how fast ST processes completions.

> Execution time of `generate_completions()` is already round about 1.4s on my Ryzen 5600X box. Note that this part is not that relevant to the issue. It happens on plugin...

I've mentioned this before but will say it again: in case of the LSP, we are creating completions on the async thread so while the completions can be slow to...

> 3\. Call set_completions (and create the items) in a background thread So you are also mentioning calling `set_completions` on the async thread... We have this code in LSP: ```py...

Not sure if that's feasible in all cases. If a plugin has to interact with `*_async` ST APIs then introducing another background thread to the mix can result in race...

ST also seems to have special handling for when calling ST API from async thread - it blocks the async thread until task on the main thread is done. A...

Just to narrow down the issue can you try running `bun run build`? Does it produce the same error? Also maybe try with npm/node to see if it might be...

Yes but the point is that git should do it for me and fail the commit if there are errors. AI told me about https://pre-commit.com/. It wouldn't be as automatic...

Sounds familiar. I've said this before:  command in a text version: ```js { "keys": ["super+alt+left"], "command": "prev_os_tab", }, ``` I've disabled/changed the key-binding which...