[Bug]: Unable to index https://github.com/bazelbuild/bazel-buildfarm

[amishra-u]

What happened?

The aspect is very heavy, requiring numerous dependencies to function. This makes it difficult to consume current implementation as an injected dependency, as the consuming repository would also need to have dependencies on all imported dependencies by aspect. Which almost makes this unusable for most of the cases

Steps to Reproduce

Tried to use scip gereration for open source repo, buildfarm. and wasn't able to make it work since it required many conflict resolution.

scip-lsp should work out of the box and consumer should not worry about resolving confilcts to use it.

Environment

Not OS dependent

Language Server Logs

SCIP Generation Logs

SCIP Index Information

Reproducible Sample

No response

Additional Context

No response

Code of Conduct

• I agree to follow this project's contribution guidelines

[murray-stripe]

This sounds related to #2. I've also hit this issue internally at Stripe and the workaround for us has been to:

0. Pre-build the lsp go binary and deploy-jars (tools) for the aspect in a tarball
1. Import these into the repository separately
2. Copy all the code under bsp_server into the repo and make adjustments to the tool paths

#2 seems relevant to creating an artifact that has all the necessary bits, but my last point about copying bsp_server is still a bit of a sticking point. Probably need a way to package up the python code as well (maybe a shiv).

Maybe the one thing that is not mentioned (currently) in #2 is that really all of this packaged "stuff" should be bundled with the VS Code extension and the extension itself should take care of wiring everything up the Bazel repository.