Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Roots Scan Stuck - ahash #16382

Closed
andre-di opened this issue Jan 17, 2024 · 3 comments · Fixed by #16383
Closed

Roots Scan Stuck - ahash #16382

andre-di opened this issue Jan 17, 2024 · 3 comments · Fixed by #16383
Assignees
Labels
C-bug Category: bug

Comments

@andre-di
Copy link

rust-analyzer version: 0.4.1809-standalone (0333646 2024-01-16)

rustc version: rustc 1.77.0-nightly (098d4fd74 2024-01-16)

relevant settings:

{
    "rust-analyzer.linkedProjects": [
        ".\\Cargo.toml"   
    ],
    "rust-analyzer.check.command": "clippy",
    "rust-analyzer.server.extraEnv": { "RA_LOG": "info" }
}

Hi. My main problem is that rust analyzer seems to be stuck when scanning target\debug\build\ahash-feb304a413e0bcb2\out

Notification

Roots Scanned: 0/329: target\debug\build\ahash-feb304a413e0bcb2\out

The other messages are for the same file the only difference is that it is in the .cargo/registry folder.

I have tried updating rust with rustup upgrade
Updated crate versions in my projects.
I have tried different versions of rust-analyzer. Does not seem to make any difference other than that preview version gives information about where it is stuck.

No warnings or errors shown in the output from the language server.

@andre-di andre-di added the C-bug Category: bug label Jan 17, 2024
@Veykril
Copy link
Member

Veykril commented Jan 17, 2024

Yep noticed this as well, note that this is solely a stuck progress message. r-a itself works fine.

@Veykril Veykril self-assigned this Jan 17, 2024
@andre-di
Copy link
Author

andre-di commented Jan 17, 2024

For me r-a does not seem to work.

Edit: In one project it does work.

Edit2:
In the project where it does not work it only seems broken in some parts of the code.
I am using axum and I have a sse handle that returns a stream which seems to be broken.

fn sse(...) -> Sse<impl Stream<Item = Result<Event, Infallible>>>
{
    let mut rx = state.sse.event_tx.subscribe();

    // r-a works.

    Sse::new(try_stream! {
        trace!("SSE DATA STREAM - BEGIN");
        ...
        // r-a broken.
    }).keep_alive(KeepAlive::default())

}

@Veykril
Copy link
Member

Veykril commented Jan 17, 2024

That's an unrelated issue. Might be r-a having difficulties with one of those macros or type inference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants