unresolved-module when using a #[path] attribute with a file outside of the current crate

[kovaxis]

rust-analyzer version: 0.3.1418-standalone

rustc version: rustc 1.67.1 (d5a82bbd2 2023-02-07)

relevant settings: All default as far as I know.

platform: rust-analyzer extension on VSCode, on Linux Mint 21 Cinnamon.

Hello,

I ran into an issue using the #[path] attribute to point to a file outside the crate.
This makes rust-analyzer run into an unresolved-module error, while cargo build and cargo run work fine.

Directory structure to reproduce the issue:

/bug/Cargo.toml
/bug/src/main.rs
/foo.rs

# /bug/Cargo.toml

[package]
name = "bug"
version = "0.1.0"
edition = "2021"

//! /bug/src/main.rs

#[path = "../../foo.rs"]
mod foo;

fn main() {
    foo::hello();
}

//! /foo.rs

pub fn hello() {
    println!("hello world!");
}

This directory structure confuses rust-analyzer but cargo itself builds and runs fine.

[lnicola]

I think this is a dupe of #3898 and maybe other issues too.

[kovaxis]

Sorry, for some reason I couldn't find that issue.