Possible bug with Workspace.lock_path initialization

[idlsoft]

A recent change added this line to uv-resolver/src/lock.rs:

let lock_path = relative_to(workspace.lock_path(), &lock_path).unwrap();

This line panicks if workspace.lock_path is initialized from Path::new("").to_path_buf(), which does happen here

        Self::from_project(
            project_root,
            Path::new(""),
            &project,
            &pyproject_toml,
            options,
        )

and here.

            let project = ProjectWorkspace::from_project(
                project_root,
                Path::new(""),
                project,
                &pyproject_toml,
                options,
            )

I'm not sure if this ever actually triggers in the existing codebase, but it seems inconsistent, probably worth a look?

[charliermarsh]

I can double-check, thanks.

[idlsoft]

FWIW replacing Path::new("") with project_root takes care of it and doesn't break any existing unit tests