You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This has been identified on the upstream cudarc project in this issue with the associated fix in an open PR here. It has not yet been merged yet though.
It's unclear to me what this additional functionality brings and whether it is actually used within Candle. I am happy to open a PR which includes pinning cuadrc to cudarc = { version = "<=0.11.6" } within affected candle-* crates if folks think it's worthwhile.
The text was updated successfully, but these errors were encountered:
Right, I also add the problem on some of my projects and fixed it by explicitely pinning cudarc in my crates but probably better for users not to have to do this so having the constraint in the main Cargo.toml file sounds good.
I'll make that change now, run it locally to see if it fixes it and then open the PR 👍🏼
Edit: From looking at the root Cargo.toml, it's pinned already. I am unfamiliar with how version constraints get passed to sub-crates. Does the change need to be applied within each sub-crate Cargo.toml?
I have opened a PR to resolve this. It was a strange issue as the version was pinned to 0.11.4 but when building Cargo was pulling the latest semver version down anyways. From looking at this stackoverflow post there seems to be some oddness around specifying exact versions!
This has been identified on the upstream
cudarc
project in this issue with the associated fix in an open PR here. It has not yet been merged yet though.It's unclear to me what this additional functionality brings and whether it is actually used within Candle. I am happy to open a PR which includes pinning
cuadrc
tocudarc = { version = "<=0.11.6" }
within affectedcandle-*
crates if folks think it's worthwhile.The text was updated successfully, but these errors were encountered: