Eric Fritz

@daxmc99 It's already present in the enterprise build and was fixed by https://github.com/sourcegraph/sourcegraph/pull/22621 in the OSS build.

Nerd-sniped by [this comment](https://github.com/sourcegraph/sourcegraph/pull/40137#pullrequestreview-1066651509). cc @eseliger

Full instructions to reproduce: - Move `base/executors` directory out of clone momentarily. Run `kubectl apply --prune -l deploy=sourcegraph -f base --recursive` to start a stack without executors at first -...

Full instructions to reproduce: - Run `docker-compose up` in the `docker-compose` directory of this branch - Visit `localhost` in a browser - Go to site settings and fill out `externalURL`...

@keegancsmith Literally no goal other than to experiment with some stuff in sg/sg, so I hackily exposed some of the main functions here. Not planning to merge this, but if...

@thenamankumar @pjlast I have no problems with this migrations 👍 The constraint is getting strictly wider, which shouldn't affect any existing data. This does, however, make buildkite angry with the...

It looks like this section could use a bit of an update: https://docs.sourcegraph.com/dev/how-to/add_support_for_a_language#syntax-highlighting-support Could we add some deeper explanation or any missing steps here? cc @sourcegraph/frontend-platform and @slimsag

Update: this also appears to happen on diff views on Sourcegraph.com, which also points to this being a langserver issue.

Can we close this with the work @creachadair has done?

@Strum355 Let's just convert this back to draft since it was just a way to play with the PR description 😛