-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with ahash
library v0.7.7 (unknown feature stdsimd
)
#250
Comments
Ran into the same issue. I am running rust nightly atm. Switching to stable allowed me to install |
This command works for me
|
Problem seems to be with the |
If you’d like to pr a bump for that and test it, I’d be happy to merge it in
On Tue, Feb 13, 2024, at 4:03 PM, Bayer wrote:
> This command works for me
>
> `cargo update ***@***.***
`
… Problem seems to be with the ahash version being used by cargo-leptos and not the local version of cargo. I still get the error and it's coming from `cargo-leptos`, ahash likely needs a bump.
—
Reply to this email directly, view it on GitHub <#250 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABVBTCJ3NIOK7BNEIIYNJLLYTP5LXAVCNFSM6AAAAABC42M522VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBSHA3TONJVGI>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Yep sounds good, just forked the repo and will see if I can get it working. |
Workaround |
Once the repo has been checked out one can run |
So the repo is up to date for this? If so I can release a new patch version |
I would assume this is the case. All I did to make it compile with the latest nightly was to checkout the default branch and after it failed building I ran |
It‘s really useful |
Hello!
I'm trying to learn Leptos (as in, I've never built a thing with it, so bear with me) and while trying to install
cargo-leptos
(andtrunk
) I ran into this error involving the installation ofahash
v0.7.7:There's already an open issue on the
aHash
repo, but honestly I don't understand the problem well enough to know if this is an aHash problem or a cargo-leptos problem. My assumption was that it's something that cargo-leptos can fix since it looks like it depends on v0.7.7 of aHash and the most recent version of aHash is v0.8.7The text was updated successfully, but these errors were encountered: