astral-sh / rye

a Hassle-Free Python Experience
https://rye.astral.sh
MIT License
13.6k stars 466 forks source link

rye build gives "Not a directory" #1137

Closed xsh005 closed 3 months ago

xsh005 commented 3 months ago

Steps to Reproduce

❯ rye self update
Updating to latest
Checking checksum
Validate updated installation
Initializing new virtualenv in /tmp/.tmpgjYOls/.venv
Python version: cpython@3.12.3
Updated!

rye 0.34.0
commit: 0.34.0 (d31340178 2024-05-20)
platform: linux (x86_64)
self-python: cpython@3.12.3
symlink support: true
uv enabled: true
❯ rye init rye-build-test
success: Initialized project in /tmp/rye-build-test
  Run `rye sync` to get started
❯ cd rye-build-test/

/tmp/rye-build-test
❯ rye sync
Reusing already existing virtualenv
Generating production lockfile: /tmp/rye-build-test/requirements.lock
Generating dev lockfile: /tmp/rye-build-test/requirements-dev.lock
Installing dependencies
   Built file:///tmp/rye-build-test                                Built 1 editable in 227ms
Installed 1 package in 0.37ms
 + rye-build-test==0.1.0 (from file:///tmp/rye-build-test)
Done!
❯ rye build
building rye-build-test
error: Not a directory (os error 20)

Expected Result

Build succeeds

Actual Result

Failed with unclear message error: Not a directory (os error 20)

Version Info

rye 0.34.0 commit: 0.34.0 (d31340178 2024-05-20) platform: linux (x86_64) self-python: cpython@3.12.3 symlink support: true uv enabled: true

Stacktrace

building rye-build-test
error: Not a directory (os error 20)

Stack backtrace:
   0: anyhow::error::<impl core::convert::From<E> for anyhow::Error>::from
   1: rye::cli::build::execute
   2: rye::cli::execute
   3: std::panicking::try
   4: rye::utils::panic::trap_bad_pipe
   5: rye::main
   6: std::sys_common::backtrace::__rust_begin_short_backtrace
   7: std::rt::lang_start::{{closure}}
   8: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once
             at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/core/src/ops/function.rs:284:13
   9: std::panicking::try::do_call
             at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/std/src/panicking.rs:552:40
  10: std::panicking::try
             at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/std/src/panicking.rs:516:19
  11: std::panic::catch_unwind
             at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/std/src/panic.rs:146:14
  12: std::rt::lang_start_internal::{{closure}}
             at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/std/src/rt.rs:148:48
  13: std::panicking::try::do_call
             at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/std/src/panicking.rs:552:40
  14: std::panicking::try
             at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/std/src/panicking.rs:516:19
  15: std::panic::catch_unwind
             at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/std/src/panic.rs:146:14
  16: std::rt::lang_start_internal
             at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/std/src/rt.rs:148:20
  17: main
Zander-1024 commented 3 months ago

Unable to reproduce

xsh005 commented 3 months ago

Maybe due to me using a system managed python