Closed persello closed 9 months ago
Running cargo install --path .
from the cargo-espflash
folder produces the same issue.
The result is the following: the cargo-espflash
binary located in target/release
and the one located in /Users/persello/.cargo/bin/cargo-espflash
are the same (checked with diff
and cmp
). The first one runs without issues, the second one crashes.
I think that the issue may come from the location of the resulting binary, but I don't know how to debug it.
macOS 14 has not been released, so I'm not surprised you're experiencing issues. cargo-espflash
installs just fine using macOS 13.5.1 on both x86_64 and arm64.
I need to be productive so I will not be installing an unstable and unreleased version of macOS, if you want to debug the issue and submit a fix please feel free, but I will not be updating my OS until there has been at least the official release and one subsequent patch release, sorry.
Sonoma was just released. Problem still there
There is now an upstream issue tracking this (https://github.com/mitsuhiko/rye/issues/428), I will leave this issue open until that is resolved, but my hands are tied until there is a new release with a fix.
Edit: sorry, misread that issue the other day. Regardless, a good reference until whichever dependency is causing this gets updated.
Sonoma was just released. Problem still there
macOS Sonoma has not been released. It will be released September 26, 2023.
There is now an upstream issue tracking this (mitsuhiko/rye#428)
Upstream for this issue is curl, where I've now filed a bug report: https://github.com/curl/curl/issues/11893
Running on OSX Sonoma (non-beta) here, works fine for me except some minor issues reported in https://github.com/esp-rs/espflash/issues/436#issuecomment-1749949042
👋
Upstream curl issue had been fixed, new curl-sys
version had been released and seems to work on Sonoma.
See https://github.com/alexcrichton/curl-rust/issues/524#issuecomment-1753070751 for more details.
I updated my M1 Mac Mini to Sonoma today, and running cargo install cargo-espflash espflash
installed both applications successfully.
Since the upstream issue is now closed and a few users have reported that it was working for them, I will be closing the issue. If the issue is still present for anyone, feel free to reopen it.
If I install
cargo-espflash
withcargo install cargo-espflash
and I runcargo espflash
, this is what I get:If I run
espflash
only, I don't run into this kind of issue.Building v2.0.1 of
cargo-espflash
withcargo run --release --bin cargo-espflash -- espflash
produces an executable that doesn't display this issue.I am using macOS 14.0 23A5312d on arm64.