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

master branch broken on 1.60.0-nightly #33

Closed
smklein opened this issue Jan 24, 2022 · 1 comment
Closed

master branch broken on 1.60.0-nightly #33

smklein opened this issue Jan 24, 2022 · 1 comment

Comments

@smklein
Copy link
Contributor

smklein commented Jan 24, 2022

To repro:

$ rustup update
$ cargo build

Output:

error: could not compile `slack-chat-api` due to previous error
warning: build failed, waiting for other jobs to finish...
error: future cannot be sent between threads safely
   --> slack/src/lib.rs:425:5
    |
425 |     #[async_recursion]
    |     ^^^^^^^^^^^^^^^^^^ future created by async block is not `Send`
    |
    = help: the trait `Sync` is not implemented for `core::fmt::Opaque`
note: future is not `Send` as this value is used across an await
   --> slack/src/lib.rs:433:66
    |
433 |                 bail!("status code: {}, body: {}", s, resp.text().await?);
    |                 -------------------------------------------------^^^^^^--
    |                 |                                                |
    |                 |                                                await occurs here, with `$crate::__export::format_args!($($arg)*)` maybe used later
    |                 has type `ArgumentV1<'_>` which is not `Send`
    |                 `$crate::__export::format_args!($($arg)*)` is later dropped here
    = note: required for the cast to the object type `dyn std::future::Future<Output = Result<FormattedMessageResponse, anyhow::Error>> + Send`
    = note: this error originates in the attribute macro `async_recursion` (in Nightly builds, run with -Z macro-backtrace for more info)
@jessfraz
Copy link
Contributor

fixed and pinned

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

No branches or pull requests

2 participants