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
Running a cargo check on a project with an indy-vdr 0.3.1 or 0.3.0 dependency will fail to compile due to mismatching types. This has to do with the different versions of indy-data-types and indy-utils that indy-vdr depends on, which under certain circumstances can cause indy-vdr to be consuming two different versions of indy-utils.
e.g. a cargo tree under a project with a single dependency on indy-vdr = "=0.3.0":
error[E0599]: no function or associated item named `from_str` found for struct `RevocationRegistryId` in the current scope
--> /Users/gmulhearne/.cargo/registry/src/github.com-1ecc6299db9ec823/indy-vdr-0.3.0/src/ffi/ledger.rs:454:54
|
454 | let revoc_reg_def_id = RevocationRegistryId::from_str(revoc_reg_def_id.as_str())?;
| ^^^^^^^^ function or associated item not found in `RevocationRegistryId`
|
= help: items from traits can only be used if the trait is in scope
help: the following trait is implemented but not in scope; perhaps add a `use` for it:
|
1 | use indy_utils::qualifiable::Qualifiable;
|
error[E0277]: `?` couldn't convert the error to `common::error::VdrError`
--> /Users/gmulhearne/.cargo/registry/src/github.com-1ecc6299db9ec823/indy-vdr-0.3.0/src/ffi/ledger.rs:455:85
|
455 | let revoc_reg_def_type = RegistryType::from_str(revoc_reg_def_type.as_str())?;
| ^ the trait `From<indy_data_types::ConversionError>` is not implemented for `common::error::VdrError`
|
= note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
= help: the following other types implement trait `From<T>`:
<common::error::VdrError as From<(common::error::VdrErrorKind, M)>>
<common::error::VdrError as From<common::error::VdrErrorKind>>
<common::error::VdrError as From<indy_utils::ConversionError>>
<common::error::VdrError as From<indy_utils::ValidationError>>
<common::error::VdrError as From<networker::zmq::zmq::Error>>
= note: required because of the requirements on the impl of `FromResidual<Result<Infallible, indy_data_types::ConversionError>>` for `Result<_, common::error::VdrError>`
error[E0599]: no method named `to_unqualified` found for reference `&SchemaId` in the current scope
--> /Users/gmulhearne/.cargo/registry/src/github.com-1ecc6299db9ec823/indy-vdr-0.3.0/src/ledger/request_builder.rs:418:21
|
418 | let id = id.to_unqualified();
| ^^^^^^^^^^^^^^ method not found in `&SchemaId`
|
= help: items from traits can only be used if the trait is in scope
help: the following trait is implemented but not in scope; perhaps add a `use` for it:
|
1 | use indy_utils::qualifiable::Qualifiable;
|
I'm unsure of the best solution to this issue, in general, the cross-dependencies happening in indy-shared-rs seem risky imo
The text was updated successfully, but these errors were encountered:
Running a
cargo check
on a project with an indy-vdr 0.3.1 or 0.3.0 dependency will fail to compile due to mismatching types. This has to do with the different versions ofindy-data-types
andindy-utils
that indy-vdr depends on, which under certain circumstances can cause indy-vdr to be consuming two different versions ofindy-utils
.e.g. a
cargo tree
under a project with a single dependency onindy-vdr = "=0.3.0"
:this causes errors such as the following:
I'm unsure of the best solution to this issue, in general, the cross-dependencies happening in indy-shared-rs seem risky imo
The text was updated successfully, but these errors were encountered: