@olafurpg OK, thanks. I will merge this so that we can get it deployed on Sourcegraph.com and fix the issue there. I'll separately ensure another code intel team member follows up on Monday morning to see about patching this into 4.0 and what else (if anything) is needed to fix this issue comprehensively. cc @lguychard

@chrismwendt (https://github.com/sourcegraph/sourcegraph/pull/42055#pullrequestreview-1119456090):

LGTM2, this essentially restores the code from prior to https://github.com/sourcegraph/sourcegraph/pull/41128, specifically this part: ...

Do you or @olafurpg know why the lookup in additionalLanguages was removed when the code was ported over? I just want to see if there was some reason for doing that, and this PR that reverts it would have unintended consequences.

I don't know, maybe it was some kind of copy-paste mistake.

I don't think this was caused by a copy-paste mistake. The spec.languageID === languageID || spec.additionalLanguages?.includes(languageID) condition doesn't exist in the original code-intel-extensions repo

https://sourcegraph.com/search?q=context:global+repo:code-intel-extensions+additionalLanguages&patternType=lucky

From what I can tell, additional languages were only used by the extension template generator to register an onLanguage:LANGUAGE activation event. The copy-pasted code came from the activate function

export const activate = async (context: sourcegraph.ExtensionContext = DUMMY_CTX): Promise<void> => {
    const languageSpec = languageSpecs.find(spec => spec.languageID === languageID)
    if (languageSpec === undefined) {
        throw new Error(`Unknown language ${languageID}`)
    }

Source https://sourcegraph.com/github.com/sourcegraph/code-intel-extensions@b97feb343cbe5d1b03582181ee13fd459587db91/-/blob/template/src/extension.ts?L62-66

@sqs Nice job finding the root cause of the issue! I spent a while trying to understand the root cause of the problem before opening the but didn't understand what was going on