rust-lang / rust-lang/rust-analyzer

`clippy` fork bomb

Open
#18,851 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-bug
Dominant language
Rust
Stars
16.9k
Forks
2.2k
Avg merge
1d 12h
Merged PRs (30d)
72

Description

rust-analyzer version: based off of add096303324 https://github.com/RoloEdits/rust-analyzer/tree/build

rustc version: rustc 1.83.0 (90b35a623 2024-11-26)

editor or extension: helix

relevant settings: N/A

Summary

After opening up the zed repo and trying to check the source code, for example the breadcrumbs.rs, and doing a hover action, it eventually begins to lag as clippy processes are started over and over.

image

Reproduction Steps

helix_fork_bomb

Helix log

https://gist.github.com/RoloEdits/cbabfa4ab230019d8795111c69029063

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Helix log gist and the hover path involving breadcrumbs.rs in the zed repository. Trace why clippy processes are repeatedly started after hover or checking actions. Done means reproducing the report no longer causes repeated clippy launches or progressive editor lag.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
devtools, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.