Skip to content

Deploy on crates.io #14

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

Closed
hug-dev opened this issue Jan 27, 2020 · 1 comment
Closed

Deploy on crates.io #14

hug-dev opened this issue Jan 27, 2020 · 1 comment
Labels
bug Something isn't working

Comments

@hug-dev
Copy link
Member

hug-dev commented Jan 27, 2020

Because of a Cargo bug (rust-lang/cargo#6961), building Parsec's tests will fail if the test client is using a different version of the interface than the service itself.

Example:

error[E0308]: mismatched types
  --> tests/per_provider/persistent_after.rs:50:5
   |
50 | /     assert_eq!(
51 | |         client
52 | |             .destroy_key(key_name)
53 | |             .expect_err("This key should have been destroyed."),
54 | |         ResponseStatus::KeyDoesNotExist
55 | |     );
   | |______^ expected enum `parsec_interface::requests::response_status::ResponseStatus`, found a different enum `parsec_interface::requests::response_status::ResponseStatus`
   |
   = note: expected type `parsec_interface::requests::response_status::ResponseStatus` (enum `parsec_interface::requests::response_status::ResponseStatus`)
              found type `parsec_interface::requests::response_status::ResponseStatus` (enum `parsec_interface::requests::response_status::ResponseStatus`)
note: Perhaps two different versions of crate `parsec_interface` are being used?
  --> tests/per_provider/persistent_after.rs:50:5
   |
50 | /     assert_eq!(
51 | |         client
52 | |             .destroy_key(key_name)
53 | |             .expect_err("This key should have been destroyed."),
54 | |         ResponseStatus::KeyDoesNotExist
55 | |     );
   | |______^
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
@hug-dev hug-dev added the bug Something isn't working label Jan 27, 2020
@hug-dev
Copy link
Member Author

hug-dev commented Feb 5, 2020

It's on 🚀
https://crates.io/crates/parsec-interface

@hug-dev hug-dev closed this as completed Feb 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant