Skip to content
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

unresolved import dispatching::repls #770

Closed
Turbo87 opened this issue Nov 17, 2022 · 4 comments · Fixed by #771
Closed

unresolved import dispatching::repls #770

Turbo87 opened this issue Nov 17, 2022 · 4 comments · Fixed by #771
Assignees
Labels
K-bug Kind: bug

Comments

@Turbo87
Copy link
Contributor

Turbo87 commented Nov 17, 2022

After trying to update from v0.11.0 to v0.11.1 I'm seeing the following error:

Checking teloxide v0.11.1
error[E0432]: unresolved import `dispatching::repls`
  --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/teloxide-0.11.1/src/lib.rs:64:22
   |
64 | pub use dispatching::repls::{commands_repl, commands_repl_with_listener};
   |                      ^^^^^ could not find `repls` in `dispatching`

error[E0432]: unresolved import `crate::dispatching::repls`
 --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/teloxide-0.11.1/src/prelude.rs:9:25
  |
9 |     dialogue::Dialogue, repls::CommandReplExt as _, Dispatcher, HandlerExt as _,
  |                         ^^^^^ could not find `repls` in `dispatching`

Note that I've disabled the default-features since my application only needs a small subset of the defaults:

teloxide = { version = "=0.11.0", default-features = false, features = ["rustls"] }

I assume that the dispatching::repls import should still be guarded by a feature gate though to avoid these compile errors :)

@Turbo87 Turbo87 added the K-bug Kind: bug label Nov 17, 2022
@WaffleLapkin
Copy link
Member

WaffleLapkin commented Nov 17, 2022

Again? I thought we already fixed that a couple of versions ago (#462)... We should really setup a better CI job, that tests with all feature combinations

@Turbo87
Copy link
Contributor Author

Turbo87 commented Nov 17, 2022

I assume that the introduction of the deprecations has caused this. #771 should fix it :)

@Hirrolot
Copy link
Collaborator

I've just released teloxide v0.11.2 and yanked v0.11.1. You should be able to upgrade to v0.11.2 with the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
K-bug Kind: bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants