-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
compilation stuck while resolving futures_async_stream #103147
Comments
Probably I'll get some easy-to-reproduce examples... |
The difference:
where in nightly-07-29
Note that the latest nightly has an extra |
Not related to futures_async_stream. Need investigate where are the 4000+ obligations from. cc @xxchan let's close for now until we find the root cause and submit another issue? |
|
Code
It seems that Rust is very slow with resolving futures_async_stream. It took about 1sec for each resolving. As a comparison, previous builds only have 0 obligations for all these things.
Originally posted by @skyzh in risingwavelabs/risingwave#5119 (comment)
And we have located the problem occurs on this function: https://github.com/risingwavelabs/risingwave/blob/2c5bc306cb063376e3497bc27f14f80ed15a6a97/src/stream/src/executor/hash_join.rs#L604-L605
After removing the
#[for_await]
in the function body, it will compiles quickly.I expected to see this happen: it compiles.
Instead, this happened: it got stuck.
Version it worked on
It most recently worked on: nightly-2022-07-29
Version with regression
rustc --version --verbose
:Backtrace
Backtrace
The text was updated successfully, but these errors were encountered: