Failed to run fleet with an os error: no such file or directory

[JmPotato]

Describe the bug

I try to run fleet build --release with my repo and it just prints out this error without any further information.

To Reproduce

Steps to reproduce the behavior:

1. Install fleet with curl -L get.fleet.rs | sh on macOS.
2. Clone https://github.com/tikv/tikv
3. fleet build --release

Expected behavior

The building should start normally.

Screenshots

As above.

Desktop (please complete the following information):

• OS: macOS 12.3.1 (21E258)

[suptejas]

@VarunPotti and I are currently implementing a fix for a similar issue faced by another user, will keep you posted 😄

[VarunPotti]

Hey @JmPotato the bug has been fixed! Please run cargo install fleet-rs --force 😀.

[suptejas]

@JmPotato Let me know if this solved it for you, we'll close the issue then!

[IAMISSAM]

Hello, i have the same issue, and with installing via cargo install fleet-rs --force i still have the same issue

I'm on macOS 12.3.1, fleet version says 0.0.7, i was on nightly toolchain but i tried switch to stable, uninstall and reinstall fleet, but still

[VarunPotti]

Hey @IAMISSAM, can you share the fleet.toml file? And if rd_enabled is set to true please change that to false, the issue should be fixed.

[IAMISSAM]

Hello, here is my fleet.toml :

rd_enabled = true
fleet_id = "83504b5d-adbb-41a7-9a50-4815c347aaea"

[build]
sccache = "/Users/issam/.cargo/bin/sccache"

When i disable rd_enabled, i have the same issue

[VarunPotti]

I see, is the target directory created?

[IAMISSAM]

No, i don't see any target directory inside my project

[VarunPotti]

What is the output cargo run gives? Does it throw a similar error?

[IAMISSAM]

cargo run works fine, and the program is running

[VarunPotti]

I see, will look into it, the ${PWD}/.cargo/config.toml file is created right?

[IAMISSAM]

Inside the project directory, there is no .cargo directory

[VarunPotti]

That must be the issue will look into this.

[VarunPotti]

Hey @IAMISSAM, I tried building on MacOS 11 https://github.com/VarunPotti/fleet-actions/runs/6146796095?check_suite_focus=true, and it works! I seem to have fixed the error I will merge it into the master branch and publish this version into cargo, will notify you when done 😁

[VarunPotti]

Yep published now along with a github workflow to check if everything works! So you can run cargo install fleet-rs --force and you will be good to go!

[suptejas]

Let us know if this issue is resolved!

[IAMISSAM]

Yeah, can confirm this is working now, thanks

[JmPotato]

@VarunPotti @suptejas Hi, after upgrading the fleet-rs, there is something wrong with the split-debuginfo config field.

[VarunPotti]

Hey @JmPotato, what version of cargo, rustc are you running? split-debuginfo='...' is specified in the documentation so it must work fine

[messense]

Hey @JmPotato, what version of cargo, rustc are you running? split-debuginfo='...' is specified in the documentation so it must work fine

I think you may have misunderstood that split-debuginfo = '...' # Platform-specific. in the docs is a valid option. To me it looks like the author simply don't want to write out platform specific value for split-debuginfo in the docs not that ... is a valid option.

See also https://doc.rust-lang.org/rustc/codegen-options/index.html#split-debuginfo

cc https://github.com/napi-rs/napi-rs/discussions/1246