influxdata / influxdata/influxdb
Make LSP more resilient to async delays
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
We have a couple of interfaces to the LSP that require async requests. As the duration of these requests are outside of our control, and the level of precaching required to resolve within the current resolution window is incongruent with our pricing models, the ask is for the LSP to not time out while waiting for the resource calls to resolve.
related: https://github.com/influxdata/influxdb/issues/18575
related: https://github.com/influxdata/influxdb/issues/18574
related: https://github.com/influxdata/idpe/issues/7664
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 reading the LSP's asynchronous request interfaces and the related issues 18575, 18574, and idpe#7664 to understand the affected resource calls. Define how requests should behave when those calls exceed the current resolution window; done means the LSP remains usable without timing out while the calls are still pending.
Written by the indexing model from the issue text.
Assessment
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100