Launcher mode issues
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 2k
- Forks
- 281
- Avg merge
- 2h 14m
- Merged PRs (30d)
- 6
Description
We're experimenting with a new launching mechanism that is aimed to allow the Ruby LSP to be more resilient to Bundler related issues. The rollout is currently at 5% of users.
If you encounter any issues, please report it here, so that we can address it and continue the gradual rollout.
If necessary, you can turn off the launcher mode temporarily by adding this to the VS Code's JSON settings:
{
"rubyLsp.featureFlags": {
"launcher": false,
}
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing and documenting a concrete failure in the experimental launcher mode; the issue names no source file, test, or specific failing behavior. Compare behavior with the launcher disabled via the rubyLsp.featureFlags.launcher VS Code setting, and consider the work complete only when a reproducible problem and expected fix are defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100