Diem: Broken MIR: generator contains type ...

Created on 18 Jun 2019  ·  5Comments  ·  Source: diem/diem

🐛 Bug

When running ./scripts/cli/start_cli_testnet.sh, the script failed:

failed to run custom build command for backtrace-sys v0.1.28

then fixed this with brew doctor related commands

```mkdir /tmp/includes
brew doctor 2>&1 | grep "/usr/local/include/" | awk '{$1=$1;print}' | xargs -I _ mv _ /tmp/includes


but now have this:

error: internal compiler error: src/librustc_mir/transform/generator.rs:714: Broken MIR: generator contains type std::option::Option in MIR, but typeck only knows about for<'r, 's, 't0, 't1, 't2, 't3, 't4, 't5, 't6, 't7, 't8, 't9, 't10, 't11, 't12, 't13, 't14> {&'r mut connectivity_manager::ConnectivityManager, std::vec::Vec, fn(std::vec::IntoIter) -> as std::iter::IntoIterator>::IntoIter { as std::iter::IntoIterator>::into_iter}, std::vec::IntoIter, types::account_address::AccountAddress, impl core::future::future::Future, (), std::vec::Vec<(&'t0 types::account_address::AccountAddress, &'t1 std::vec::Vec)>, fn(std::vec::IntoIter<(&'t2 types::account_address::AccountAddress, &'t3 std::vec::Vec)>) -> )> as std::iter::IntoIterator>::IntoIter {)> as std::iter::IntoIterator>::into_iter}, std::vec::IntoIter<(&'t4 types::account_address::AccountAddress, &'t5 std::vec::Vec)>, std::vec::IntoIter<(&'t6 types::account_address::AccountAddress, &'t7 std::vec::Vec)>, std::vec::IntoIter<(&'t8 types::account_address::AccountAddress, &'t9 std::vec::Vec)>, (&'t10 types::account_address::AccountAddress, &'t11 std::vec::Vec), &'t12 types::account_address::AccountAddress, &'t13 std::vec::Vec, impl core::future::future::Future}
--> network/src/connectivity_manager/mod.rs:119:44
|
119 | async fn check_connectivity(&mut self) {
| ____________________________________________^
120 | | // Ensure we are only connected to eligible peers.
121 | | let stale_connections: Vec<_> = self
122 | | .connected
... |
180 | | }
181 | | }
| |_____^

thread 'rustc' panicked at 'Box', src/librustc_errors/lib.rs:578:9
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace.
error: aborting due to previous error

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports

note: rustc 1.37.0-nightly (b25ee6449 2019-06-17) running on x86_64-apple-darwin

note: compiler flags: -C debuginfo=2 -C incremental --crate-type lib

note: some of the compiler flags provided by cargo are hidden

error: Could not compile network.
warning: build failed, waiting for other jobs to finish...
error: build failed
```

To reproduce

  1. git clone https://github.com/libra/libra.git && cd libra
  2. ./scripts/dev_setup.sh
  3. ./scripts/cli/start_cli_testnet.sh

Expected Behavior

CLI Client Build

System information

latest version cloned from GitHub
rustc 1.37.0-nightly (b25ee6449 2019-06-17)
MacOs Mojave 10.14.5

bug

All 5 comments

You obviously need to report this to https://github.com/rust-lang/rust/

@Kixunil sorry, how is this "obvious"?

The message itself says it:

note: the compiler unexpectedly panicked. this is a bug.


note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports

The link points to that repository, not this one.

@Kixunil are you still experiencing this problem? Also did you follow up on @rollsmorr comment and report it on the Rust github?

I haven't been able to repro this. If the problem still persists please reopen the issue.

Was this page helpful?
0 / 5 - 0 ratings