Cargo install failing

I can't seem to install evcxr_jupyter with cargo. I tried
brew install zeromq pkg-config
cargo install evcxr_jupyter --no-default-features

But I get a long stack trace output.
error[E0599]: no method named `sweep` found for struct `QueryTable<'_, TraitImplsInCrateQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, TraitImplsInCrateQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, TraitImplsInCrateQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, TraitImplsInCrateQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, TraitImplsInDepsQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, TraitImplsInDepsQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, TraitImplsInDepsQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, TraitImplsInDepsQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, AssociatedTyDataQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, AssociatedTyDataQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, AssociatedTyDataQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, AssociatedTyDataQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, TraitDatumQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, TraitDatumQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, TraitDatumQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, TraitDatumQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, StructDatumQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, StructDatumQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, StructDatumQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, StructDatumQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, ImplDatumQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, ImplDatumQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, ImplDatumQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, ImplDatumQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, FnDefDatumQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, FnDefDatumQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, FnDefDatumQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, FnDefDatumQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, ReturnTypeImplTraitsQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, ReturnTypeImplTraitsQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, ReturnTypeImplTraitsQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, ReturnTypeImplTraitsQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternCallableDefQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, InternCallableDefQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternCallableDefQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, InternCallableDefQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternTypeParamIdQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, InternTypeParamIdQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternTypeParamIdQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, InternTypeParamIdQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternImplTraitIdQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, InternImplTraitIdQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternImplTraitIdQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, InternImplTraitIdQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternClosureQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, InternClosureQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternClosureQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, InternClosureQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, AssociatedTyValueQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, AssociatedTyValueQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, AssociatedTyValueQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, AssociatedTyValueQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, TraitSolveQueryQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, TraitSolveQueryQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, TraitSolveQueryQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, TraitSolveQueryQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, FileSymbolsQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, FileSymbolsQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, FileSymbolsQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, FileSymbolsQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, LibrarySymbolsQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, LibrarySymbolsQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, LibrarySymbolsQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, LibrarySymbolsQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, LocalRootsQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, LocalRootsQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, LocalRootsQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, LocalRootsQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, LibraryRootsQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, LibraryRootsQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, LibraryRootsQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, LibraryRootsQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, LineIndexQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, LineIndexQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, LineIndexQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, LineIndexQuery>`
...
132 | /         sweep_each_query![
133 | |             // SourceDatabase
134 | |             base_db::ParseQuery
135 | |             base_db::CrateGraphQuery
...   |
213 | |             crate::LineIndexQuery
214 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternMacroQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, InternMacroQuery>`
...
222 | /         sweep_each_query![
223 | |             // AstDatabase
224 | |             hir::db::InternMacroQuery
225 | |
...   |
238 | |             hir::db::InternTypeParamIdQuery
239 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternMacroQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, InternMacroQuery>`
...
222 | /         sweep_each_query![
223 | |             // AstDatabase
224 | |             hir::db::InternMacroQuery
225 | |
...   |
238 | |             hir::db::InternTypeParamIdQuery
239 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternFunctionQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, InternFunctionQuery>`
...
222 | /         sweep_each_query![
223 | |             // AstDatabase
224 | |             hir::db::InternMacroQuery
225 | |
...   |
238 | |             hir::db::InternTypeParamIdQuery
239 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternFunctionQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, InternFunctionQuery>`
...
222 | /         sweep_each_query![
223 | |             // AstDatabase
224 | |             hir::db::InternMacroQuery
225 | |
...   |
238 | |             hir::db::InternTypeParamIdQuery
239 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternStructQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, InternStructQuery>`
...
222 | /         sweep_each_query![
223 | |             // AstDatabase
224 | |             hir::db::InternMacroQuery
225 | |
...   |
238 | |             hir::db::InternTypeParamIdQuery
239 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternStructQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, InternStructQuery>`
...
222 | /         sweep_each_query![
223 | |             // AstDatabase
224 | |             hir::db::InternMacroQuery
225 | |
...   |
238 | |             hir::db::InternTypeParamIdQuery
239 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternUnionQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, InternUnionQuery>`
...
222 | /         sweep_each_query![
223 | |             // AstDatabase
224 | |             hir::db::InternMacroQuery
225 | |
...   |
238 | |             hir::db::InternTypeParamIdQuery
239 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternUnionQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, InternUnionQuery>`
...
222 | /         sweep_each_query![
223 | |             // AstDatabase
224 | |             hir::db::InternMacroQuery
225 | |
...   |
238 | |             hir::db::InternTypeParamIdQuery
239 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternEnumQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, InternEnumQuery>`
...
222 | /         sweep_each_query![
223 | |             // AstDatabase
224 | |             hir::db::InternMacroQuery
225 | |
...   |
238 | |             hir::db::InternTypeParamIdQuery
239 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternEnumQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, InternEnumQuery>`
...
222 | /         sweep_each_query![
223 | |             // AstDatabase
224 | |             hir::db::InternMacroQuery
225 | |
...   |
238 | |             hir::db::InternTypeParamIdQuery
239 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternConstQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, InternConstQuery>`
...
222 | /         sweep_each_query![
223 | |             // AstDatabase
224 | |             hir::db::InternMacroQuery
225 | |
...   |
238 | |             hir::db::InternTypeParamIdQuery
239 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternConstQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, InternConstQuery>`
...
222 | /         sweep_each_query![
223 | |             // AstDatabase
224 | |             hir::db::InternMacroQuery
225 | |
...   |
238 | |             hir::db::InternTypeParamIdQuery
239 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternStaticQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, InternStaticQuery>`
...
222 | /         sweep_each_query![
223 | |             // AstDatabase
224 | |             hir::db::InternMacroQuery
225 | |
...   |
238 | |             hir::db::InternTypeParamIdQuery
239 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternStaticQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, InternStaticQuery>`
...
222 | /         sweep_each_query![
223 | |             // AstDatabase
224 | |             hir::db::InternMacroQuery
225 | |
...   |
238 | |             hir::db::InternTypeParamIdQuery
239 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternTraitQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, InternTraitQuery>`
...
222 | /         sweep_each_query![
223 | |             // AstDatabase
224 | |             hir::db::InternMacroQuery
225 | |
...   |
238 | |             hir::db::InternTypeParamIdQuery
239 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternTraitQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, InternTraitQuery>`
...
222 | /         sweep_each_query![
223 | |             // AstDatabase
224 | |             hir::db::InternMacroQuery
225 | |
...   |
238 | |             hir::db::InternTypeParamIdQuery
239 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternTypeAliasQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, InternTypeAliasQuery>`
...
222 | /         sweep_each_query![
223 | |             // AstDatabase
224 | |             hir::db::InternMacroQuery
225 | |
...   |
238 | |             hir::db::InternTypeParamIdQuery
239 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternTypeAliasQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, InternTypeAliasQuery>`
...
222 | /         sweep_each_query![
223 | |             // AstDatabase
224 | |             hir::db::InternMacroQuery
225 | |
...   |
238 | |             hir::db::InternTypeParamIdQuery
239 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternImplQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, InternImplQuery>`
...
222 | /         sweep_each_query![
223 | |             // AstDatabase
224 | |             hir::db::InternMacroQuery
225 | |
...   |
238 | |             hir::db::InternTypeParamIdQuery
239 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternImplQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, InternImplQuery>`
...
222 | /         sweep_each_query![
223 | |             // AstDatabase
224 | |             hir::db::InternMacroQuery
225 | |
...   |
238 | |             hir::db::InternTypeParamIdQuery
239 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternTypeParamIdQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:111:32
    |
111 |                   $q.in_db(self).sweep(sweep);
    |                                  ^^^^^ method not found in `QueryTable<'_, InternTypeParamIdQuery>`
...
222 | /         sweep_each_query![
223 | |             // AstDatabase
224 | |             hir::db::InternMacroQuery
225 | |
...   |
238 | |             hir::db::InternTypeParamIdQuery
239 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0599]: no method named `sweep` found for struct `QueryTable<'_, InternTypeParamIdQuery>` in the current scope
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_ide_db-0.0.66/src/apply_change.rs:118:32
    |
118 |                   $q.in_db(self).sweep(sweep.discard_everything());
    |                                  ^^^^^ method not found in `QueryTable<'_, InternTypeParamIdQuery>`
...
222 | /         sweep_each_query![
223 | |             // AstDatabase
224 | |             hir::db::InternMacroQuery
225 | |
...   |
238 | |             hir::db::InternTypeParamIdQuery
239 | |         ];
    | |__________- in this macro invocation
    |
    = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to 164 previous errors

Some errors have detailed explanations: E0432, E0599.
For more information about an error, try `rustc --explain E0432`.
error: could not compile `ra_ap_ide_db`

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: failed to compile `evcxr_jupyter v0.11.0`, intermediate artifacts can be found at `/var/folders/07/w9mfx9yn3z710mwsrlrtgdmm0000gp/T/cargo-installp49cJY`

Caused by:
  build failed

Yeah, same here. Completely unable to build the project.

Thanks for the report. A crate that we indirectly depend on made a breaking change without doing a proper version bump.
I've released 0.12.0 to fix it.

@davidlattimore Thanks, but installing still fails. A new error is thrown on the console
   Compiling ra_ap_hir_ty v0.0.76
error[E0658]: use of unstable library feature 'control_flow_enum': new API
 --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_hir_ty-0.0.76/src/method_resolution.rs:5:17
  |
5 | use std::{iter, ops::ControlFlow, sync::Arc};
  |                 ^^^^^^^^^^^^^^^^
  |
  = note: see issue #75744 <https://github.com/rust-lang/rust/issues/75744> for more information

error[E0658]: use of unstable library feature 'control_flow_enum': new API
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_hir_ty-0.0.76/src/method_resolution.rs:440:24
    |
440 |                 return ControlFlow::Break(());
    |                        ^^^^^^^^^^^^^^^^^^
    |
    = note: see issue #75744 <https://github.com/rust-lang/rust/issues/75744> for more information

error[E0658]: use of unstable library feature 'control_flow_enum': new API
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_hir_ty-0.0.76/src/method_resolution.rs:442:13
    |
442 |             ControlFlow::Continue(())
    |             ^^^^^^^^^^^^^^^^^^^^^
    |
    = note: see issue #75744 <https://github.com/rust-lang/rust/issues/75744> for more information

error[E0658]: use of unstable library feature 'control_flow_enum': new API
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_hir_ty-0.0.76/src/method_resolution.rs:457:62
    |
457 |     callback: &mut dyn FnMut(&Canonical<Ty>, AssocItemId) -> ControlFlow<()>,
    |                                                              ^^^^^^^^^^^^^^^
    |
    = note: see issue #75744 <https://github.com/rust-lang/rust/issues/75744> for more information

error[E0658]: use of unstable library feature 'control_flow_enum': new API
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_hir_ty-0.0.76/src/method_resolution.rs:458:6
    |
458 | ) -> ControlFlow<()> {
    |      ^^^^^^^^^^^^^^^
    |
    = note: see issue #75744 <https://github.com/rust-lang/rust/issues/75744> for more information

error[E0658]: use of unstable library feature 'control_flow_enum': new API
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_hir_ty-0.0.76/src/method_resolution.rs:497:13
    |
497 |             ControlFlow::Continue(())
    |             ^^^^^^^^^^^^^^^^^^^^^
    |
    = note: see issue #75744 <https://github.com/rust-lang/rust/issues/75744> for more information

error[E0658]: use of unstable library feature 'control_flow_enum': new API
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_hir_ty-0.0.76/src/method_resolution.rs:523:66
    |
523 |     mut callback: &mut dyn FnMut(&Canonical<Ty>, AssocItemId) -> ControlFlow<()>,
    |                                                                  ^^^^^^^^^^^^^^^
    |
    = note: see issue #75744 <https://github.com/rust-lang/rust/issues/75744> for more information

error[E0658]: use of unstable library feature 'control_flow_enum': new API
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_hir_ty-0.0.76/src/method_resolution.rs:524:6
    |
524 | ) -> ControlFlow<()> {
    |      ^^^^^^^^^^^^^^^
    |
    = note: see issue #75744 <https://github.com/rust-lang/rust/issues/75744> for more information

error[E0658]: use of unstable library feature 'control_flow_enum': new API
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_hir_ty-0.0.76/src/method_resolution.rs:583:66
    |
583 |     mut callback: &mut dyn FnMut(&Canonical<Ty>, AssocItemId) -> ControlFlow<()>,
    |                                                                  ^^^^^^^^^^^^^^^
    |
    = note: see issue #75744 <https://github.com/rust-lang/rust/issues/75744> for more information

error[E0658]: use of unstable library feature 'control_flow_enum': new API
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_hir_ty-0.0.76/src/method_resolution.rs:584:6
    |
584 | ) -> ControlFlow<()> {
    |      ^^^^^^^^^^^^^^^
    |
    = note: see issue #75744 <https://github.com/rust-lang/rust/issues/75744> for more information

error[E0658]: use of unstable library feature 'control_flow_enum': new API
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_hir_ty-0.0.76/src/method_resolution.rs:614:5
    |
614 |     ControlFlow::Continue(())
    |     ^^^^^^^^^^^^^^^^^^^^^
    |
    = note: see issue #75744 <https://github.com/rust-lang/rust/issues/75744> for more information

error[E0658]: use of unstable library feature 'control_flow_enum': new API
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_hir_ty-0.0.76/src/method_resolution.rs:625:66
    |
625 |     mut callback: &mut dyn FnMut(&Canonical<Ty>, AssocItemId) -> ControlFlow<()>,
    |                                                                  ^^^^^^^^^^^^^^^
    |
    = note: see issue #75744 <https://github.com/rust-lang/rust/issues/75744> for more information

error[E0658]: use of unstable library feature 'control_flow_enum': new API
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_hir_ty-0.0.76/src/method_resolution.rs:626:6
    |
626 | ) -> ControlFlow<()> {
    |      ^^^^^^^^^^^^^^^
    |
    = note: see issue #75744 <https://github.com/rust-lang/rust/issues/75744> for more information

error[E0658]: use of unstable library feature 'control_flow_enum': new API
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_hir_ty-0.0.76/src/method_resolution.rs:648:62
    |
648 |     callback: &mut dyn FnMut(&Canonical<Ty>, AssocItemId) -> ControlFlow<()>,
    |                                                              ^^^^^^^^^^^^^^^
    |
    = note: see issue #75744 <https://github.com/rust-lang/rust/issues/75744> for more information

error[E0658]: use of unstable library feature 'control_flow_enum': new API
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_hir_ty-0.0.76/src/method_resolution.rs:649:6
    |
649 | ) -> ControlFlow<()> {
    |      ^^^^^^^^^^^^^^^
    |
    = note: see issue #75744 <https://github.com/rust-lang/rust/issues/75744> for more information

error[E0658]: use of unstable library feature 'control_flow_enum': new API
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_hir_ty-0.0.76/src/method_resolution.rs:703:5
    |
703 |     ControlFlow::Continue(())
    |     ^^^^^^^^^^^^^^^^^^^^^
    |
    = note: see issue #75744 <https://github.com/rust-lang/rust/issues/75744> for more information

error[E0658]: use of unstable library feature 'control_flow_enum': new API
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_hir_ty-0.0.76/src/method_resolution.rs:741:62
    |
741 |     callback: &mut dyn FnMut(&Canonical<Ty>, AssocItemId) -> ControlFlow<()>,
    |                                                              ^^^^^^^^^^^^^^^
    |
    = note: see issue #75744 <https://github.com/rust-lang/rust/issues/75744> for more information

error[E0658]: use of unstable library feature 'control_flow_enum': new API
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_hir_ty-0.0.76/src/method_resolution.rs:742:6
    |
742 | ) -> ControlFlow<()> {
    |      ^^^^^^^^^^^^^^^
    |
    = note: see issue #75744 <https://github.com/rust-lang/rust/issues/75744> for more information

error[E0658]: use of unstable library feature 'control_flow_enum': new API
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_hir_ty-0.0.76/src/method_resolution.rs:745:24
    |
745 |         None => return ControlFlow::Continue(()),
    |                        ^^^^^^^^^^^^^^^^^^^^^
    |
    = note: see issue #75744 <https://github.com/rust-lang/rust/issues/75744> for more information

error[E0658]: use of unstable library feature 'control_flow_enum': new API
   --> /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_ap_hir_ty-0.0.76/src/method_resolution.rs:781:5
    |
781 |     ControlFlow::Continue(())
    |     ^^^^^^^^^^^^^^^^^^^^^
    |
    = note: see issue #75744 <https://github.com/rust-lang/rust/issues/75744> for more information

error: aborting due to 20 previous errors

For more information about this error, try `rustc --explain E0658`.
error: could not compile `ra_ap_hir_ty`

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: failed to compile `evcxr_jupyter v0.12.0`, intermediate artifacts can be found at `/tmp/cargo-installzC3O3q`

Caused by:
  build failed

@davidlattimore That works. Thanks.


Consider / evaluate non-native Serialization to session

To capture our conversation about Serialization performance and specifically Kryo
Here are some benchmarks - Kryo does well, but maybe protostuff may be even quicker..

Interesting benchmarks.
At a first look it seems that, apart from performance, Kryo seems easier to customize, has better documentation and also some OOB serializer implementation in a side project (eg CGLib proxy).
Protostuff seems more oriented on a scenario of messages serialization.
One thing we also should considered is the possibility to have in session some objects with custom serialization logic that should be executed; this happens for some Vaadin classes but could also happen for application specific classes (maybe from third party libraries).
In a custom serialization process (Kryo, protostuff or whatever)  this cases should be somehow intercepted in order to apply default java serialization.
To find out what classes should use default serialization there should be a better check than a simple  instanceof Serializable; I'm thinking about inspecting class for at least one serialization method (writeObject, readObject, writeReplace,readResolve`)

One thing we also should considered is the possibility to have in session some objects with custom serialization logic that should be executed

I agree, there could be a requirement to Serialise almost anything, so ease of customisation would be a significant factor

In a custom serialization process (Kryo, protostuff or whatever) this cases should be somehow intercepted in order to apply default java serialization.

There are many use cases for custom Serialization, but once a serialiser (eg, Kryo) is employed, I cannot think of a reason to drop back into native Java serialisation.  Could you give an example of what you are thinking of?
For Kryo certainly, and possibly others, it might be interesting to see how the registration of common Vaadin classes might affect performance - but that could be left for a second iteration.

There are many use cases for custom Serialization, but once a serialiser (eg, Kryo) is employed, I cannot think of a reason to drop back into native Java serialisation. Could you give an example of what you are thinking of?

Here I'm thinking more about deserialization; a class could have some transient fileds that will be reinitialized in readObject. As an example we can take vaadin ConnectorTracker class where in readObject there is some logic that fills the transient diffStates map.
In this case if we don't rely on default java serialization we must add a custom serializer reimplementing the existing logic; and this should be done for every class with custom logic.
So my concern is not about performance but about object integrity after deserialization

Ah, now I understand your concern.
At a quick look, the main difference here is that native deserialisation does not use a constructor, Kryo does.  Ironically, most transient field initialisation does the same as object construction, but that cannot be guaranteed - some cases may do something completely different.  So you are right, potentially there is a need to replicate all readObject() implementations.
This could be a major problem when used with code which you do not control.  I wonder if it is worth a question to the Kryo forum - this must surely be a common problem?


Added methods to support string input and output from TensorFlow.

This PR fixes https://github.com/migueldeicaza/TensorFlowSharp/issues/393. This also addressed the request in #238
Also added test to ensure that it works.

Hi Zeeshan Ahmed, I was just about to add this to TensorFlow.FSharp, thanks for the code :)

This is beautiful - Thanks for your contribution!


Revert "Fix quotes (#3)"

This reverts commit baeb432b220dd36fc03a30f9c0ea50a96a5ac8a9.
We fixed this in keybase/client instead.

@keybase/react-hackers merging this


Missing scrollbar

For longer graphs, there is no scrollbar available.
This leads to unexpected behaviour, where mouse scroll means "zoom in/out". Keyboard arrows also do not allow for moving up/down the page.
Example:
https://zazuko.github.io/SPEX/#/?url=https%3A%2F%2Fld.stadt-zuerich.ch%2Fquery&graph=https%3A%2F%2Flindas.admin.ch%2Fstadtzuerich%2Fstat%2Fviews&prefixes=wdt%3Ahttp%3A%2F%2Fwww.wikidata.org%2Fprop%2Fdirect%2F&forceIntrospection=false

The controls are similar to a geographical map component. You can move around by clicking and dragging.
But adding support for arrow keys is not a bad idea.

Arrow keys are now supported ;)

Closing in favor of the now supported other interaction methods, I considered shortly to add a graphical element to hint this, but it seems intuitive enough that there is no need.


Dynamic links short url throws platform exemption

I tried using dynamic_links plugin and able to create dynamic links. But when I tried to shorten uri using
final Uri dynamicUrl = await parameters.buildUrl();
final ShortDynamicLink shortDynamicLink = await parameters.buildShortLink();
final Uri shortUrl = shortDynamicLink.shortUrl;

and
final Uri dynamicUrl = await parameters.buildUrl();
final ShortDynamicLink shortenedLink = await DynamicLinkParameters.shortenUrl(
  Uri.parse('https://example.page.link/?link=https://example.com/&apn=com.example.android&ibn=com.example.ios'dynamicUrl),
  DynamicLinkParametersOptions(ShortDynamicLinkPathLength.unguessable),
);
final Uri shortUrl = shortenedLink.shortUrl;

but both the tries resulted me in platform exemption only. I'm using Xiaomi redmi 5A running on MIUI 10 Global 9.2.15 beta based on Android 8.1.0 for testing

@harshapulikollu
The issue at https://github.com/flutter/flutter/issues/28395 has been closed and moved here. Future collaboration on this issue will be done here.

Hi @harshapulikollu
If are you still experiencing this issue
with the latest version of Flutter and FlutterFire plugin
can you please provide your flutter doctor -v
and your and your flutter run --verbose/flutter build --verbose ?
Also, to better address the issue, would be helpful
if you could post a self contained app on github
or the steps to reproduce it.
Thank you

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of 'flutter doctor -v'  please.
All system setups can be slightly different so its always better to open new issues and reference related issues.

@iapicca I am still having this issue. I am using an Pixel 2 Emulator with API 29.
This line of code throws:
final ShortDynamicLink dynamicUrl = await parameters.buildShortLink();

It works when used with
final Uri dynamicUrl = await parameters.buildUrl();

The exact error message:
E/flutter (25847): [ERROR:flutter/lib/ui/ui_dart_state.cc(157)] Unhandled Exception: PlatformException(short_link_error, 8: , null)

Output of flutter doctor -v:
[√] Flutter (Channel stable, v1.12.13+hotfix.9, on Microsoft Windows [Version 10.0.18362.778], locale en-DE)
    • Flutter version 1.12.13+hotfix.9 at C:\Users\user\flutter
    • Framework revision f139b11009 (3 weeks ago), 2020-03-30 13:57:30 -0700
    • Engine revision af51afceb8
    • Dart version 2.7.2

[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at C:\Users\user\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 28.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)
    • All Android licenses accepted.

[√] Android Studio (version 3.6)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b04)

[√] IntelliJ IDEA Ultimate Edition (version 2019.3)
    • IntelliJ at C:\Users\user\AppData\Local\JetBrains\Toolbox\apps\IDEA-U\ch-0\193.6015.39
    • Flutter plugin version 44.0.3
    • Dart plugin version 193.6015.53

[√] VS Code (version 1.44.2)
    • VS Code at C:\Users\user\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.9.1

[√] Connected device (1 available)
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 10 (API 29) (emulator)

• No issues found!

Any solutions>>..?

#2851


fix memleak when proxy goroutine panic

Issues associated with this PR
Your PR should present related issues you want to solve.
Sign the CLA
Make sure you have signed the CLA
Solutions
You should show your solutions about the issues in your PR, including the overall solutions,
details and the changes. At this time, Chinese is allowed to describe these.
UT result
Unit Test is needed if the code is changed, your unit test should cover boundary cases, corner cases, and some exceptional cases.
And you need to show the ut result.
Benchmark
If your code involves the processing of every request, you should give the Benchmark Result
Code Style

Make sure Goimports has run
Show Golint result

Codecov Report

Merging #915 into stable will decrease coverage by <.01%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           stable     #915      +/-   ##
==========================================
- Coverage   55.63%   55.62%   -0.01%
==========================================
  Files         234      234
  Lines       23799    23803       +4
==========================================
  Hits        13240    13240
- Misses       9341     9346       +5
+ Partials     1218     1217       -1

Impacted Files
Coverage Δ

pkg/proxy/proxy.go
8.26% <0%> (-0.07%)
:arrow_down:

pkg/proxy/downstream.go
34.71% <80%> (+0.27%)
:arrow_up:

pkg/module/http2/transport.go
78.59% <0%> (-0.22%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b6af740...d00e272. Read the comment docs.


Update to 4.3.1

Current BS is 4.3.1 and I'm noticing a few issues with builder such as dropdowns having a misplaced arrow etc.

+9

^4.5.0


infiniteloop with slideBy: 'page' rewinds....

The infiniteloop works fine with sliding one item - but when I use it with slideBy: 'page' it slides back to the left. Not nice. :-/
My options:
loop:true,
autoplay: true,
margin:10,
nav:true,
slideBy:'page',
responsive:{
0:{
items:3
},
992:{
items:4
},
1200:{
items:5
}
}

I ran into this as well. loop:true and slideBy:'page' don't seem to work together.
http://codepen.io/anon/pen/RPdwdr


DEP: Execute deprecation of pinv2

Reference issue

Closes #15737
What does this implement/fix?

pinv2 has been deprecated since 1.7.0 so could be removed for 1.9.0
Additional information

I am so not looking forward to this about 😃 But better do it now than later. Thanks @j-bowhay  Do you mind adding a line to the wiki about it?

Do you mind adding a line to the wiki about it?

yep will do

There are a couple references to pinv2 in the linalg tutorial that should be cleaned up:
https://github.com/scipy/scipy/blob/62f75fa33f1a832043b53f0694693dee0fe9503a/doc/source/tutorial/linalg.rst?plain=1#L354-L359
https://github.com/scipy/scipy/blob/62f75fa33f1a832043b53f0694693dee0fe9503a/doc/source/tutorial/linalg.rst?plain=1#L404-L409

Argh. Missed those. Thanks for the heads up Warren.


docs: draft spec for mast binary format

This PR adds a new document which describes the new in-memory representation we've been discussing recently, as well as provides a draft specification for the MAST binary format. This isn't meant to be the canonical source for the specification or anything, I just found it convenient to draft it here, and figured it would be a good way to get some feedback before opening a more formal proposal in the miden-vm repo.
@bobbinth You're going to be the one most interested in what's here. Feel free to skip over the section that details aspects of the in-memory representation. Nothing has really changed there since our discussion over in the miden-vm repo, but I tried to write up a bit more of a summary/intro document to make sure I understood all the pieces more or less. The primary thing I'd like to get your opinion on is the specification of the binary format itself. It's not a formal spec, but it is precisely defined.
@greenhat Also interested in any notes you have, a lot of the details here are quite similar to the package format we're also discussing, so it should be pretty familiar already. The two formats are intended to have some synergistic properties, so that's part of the reason they are so similar.
Anyway, once you both feel like this is ready to propose in the miden-vm repo, I'll open an issue for it there. Consider this an early draft.

Looks great! I don't think I can say something in addition to what was written above, but for me it looks awesome.

One other thing I wanted to ask: would things like source locations and other debug-related data go into the data section? Or these things are not really a part of this spec and would be handled separately (i.e., via the package format)?

One other thing I forgot to clarify: would things like source locations and other debug-related data go into the data section? Or these things are not really a part of this spec and would be handled separately (i.e., via the package format)?

Actually, re-reading https://github.com/0xPolygonMiden/compiler/pull/129, I've answered my own question: debug data goes into the package but not into MAST.

This has been implemented in 0xPolygonMiden/miden-vm, more or less, so I'm closing this PR since it was primarily meant for drafting the initial spec.


Generate gulliver.js (ES5) from gulliver.es6.js (ES6)

Safari 9 can't handle the arrow functions we had in gulliver.js. Add a "build" step to generate an ES5 version.
One (unfortunate) implication of this means that when editing gulliver.es6.js we need to run npm prestart before reloading. (We should improve this later.)
Note that npm start runs this automatically, so npm start (and deploying to GCP?) should work just fine.

I added /public/js/gulliver.js to .eslintignore
because the generated file uses tabs instead of spaces.


Please to be perfect circle

Is there any way these can always be perfect circles? The oval thing is visually distracting.

Done.


Add SPI DocC support

Steps from https://blog.swiftpackageindex.com/posts/auto-generating-auto-hosting-and-auto-updating-docc-documentation/

The docc plug-in is now optimal!

Show up how? There must be feature/session I haven't caught up with yet! 😄

@finestructure SPI plug-in commands show up in the File > Package submenu:

Still early days but handy to have the option :smile:


MISSION_ITEM_REACHED is not sent

When mission point is reached, Mission::set_mission_item_reached() is called from Mission::on_active(), setting mission_result.reached to true.
But later in the Mission::on_active(),the set_mission_items() (https://github.com/PX4/Firmware/blob/master/src/modules/navigator/mission.cpp#L195) is called and the "reached" flag is reset to false here
https://github.com/PX4/Firmware/blob/master/src/modules/navigator/mission.cpp#L1364 (called from https://github.com/PX4/Firmware/blob/master/src/modules/navigator/mission.cpp#L799)
This happens before the "reached" flag is checked in the MavlinkMissionManager::send() and since the mission_result.reached is false (https://github.com/PX4/Firmware/blob/master/src/modules/mavlink/mavlink_mission.cpp#L350) the message is not sent
I have a feeling that firmware version from last year didn't have this problem.

I'm getting this here in HITL successfully. Please re-open if I missed something.

I'm sorry for inacurate report. I was bit confused that MISSION_ITEM_REACHED is sent when the whole mission is done (I expected it to be sent in every mission point), which may be expected feature. And particularly I missed the MISSION_CURRENT which works perfectly O:)
So thank you very much for directing me.


Need to automatically put .bnta file extension on type archives when saved

Version and Platform (required):

Binary Ninja Version: 4.0.4981-dev
OS: Ubuntu Linux
OS Version: 22.04
CPU Architecture: x86-64

Bug Description:
On Linux at least, it doesn't appear that the .bnta suffix is being automatically added to new type archives when they are saved.
This is problematic because the "Attach Type Library" context menu option currently requires the extension in order to select it.
Steps To Reproduce:

Open a project in Binary Ninja
Open an analysis database or file within that project
In the types browser, right-click and choose "Create Type Archive" from the context menu
Save your type archive to the project
Observe that it does not have the file extension added automatically

Expected Behavior:
The extension is added automatically.

Fixed in 4.0.4900


feat(timeline-api) Added timeline api

Description
This change adds the timeline-api to the apps
Type

[ ] Dependency upgrade
[ ] Bug fix
[x] New feature
[ ] Dev change

@williamwd we would need the following .env vars for this service
POSTGRES_USER
POSTGRES_PASSWORD
POSTGRES_HOST
POSTGRES_PORT
POSTGRES_DB_NAME=timeline
POSTGRES_DB_NAME_SHARED=shared


ArrayIndexOutOfBoundsException in scene2d.Actor.setZIndex (int index)

Issue details
If children.size = 0, then method scene2d.Actor.setZIndex causes an ArrayIndexOutOfBoundsException.
index is assigned the value -1 in the line of code:
 index = Math.min(index, children.size - 1);

Reproduction steps/code
public boolean setZIndex (int index) {
    if (index < 0) throw new IllegalArgumentException("ZIndex cannot be < 0.");
    Group parent = this.parent;
    if (parent == null) return false;
    Array<Actor> children = parent.children;
    if (children.size == 1) return false;
    index = Math.min(index, children.size - 1);
    if (children.get(index) == this) return false;
    if (!children.removeValue(this, true)) return false;
    children.insert(index, this);
    return true;
}

Version of libGDX and/or relevant dependencies
gdxVersion = 1.10.0
Stacktrace
Caused by: java.lang.ArrayIndexOutOfBoundsException: Index -1 out of bounds for length 42

Please select the affected platforms

[x] Android
[x] iOS
[x] HTML/GWT
[x] Windows
[x] Linux
[x] macOS

That should only happen if children already has size 0, in which case there's no way the next line could run either. I'm guessing the solution is to change if (children.size == 1) return false; to if (children.size <= 1) return false;, above the line in question.
`


Treatment and outcome must be single characters otherwise error is thrown

I assume this is not intended. If either is a string of more than one character then an error is thrown when creating the CausalModel object.
import random
import pandas as pd
import dowhy
from dowhy.do_why import CausalModel
z=[i for i in range(10)]
random.shuffle(z)
df = pd.DataFrame(data = {'zz': z, 'tt': range(0,10), 'bb': range(0,100,10)})
model=CausalModel(
        data = df,
        treatment='tt',
        outcome='bb',
        graph="digraph {zz -> tt;zz -> bb;tt -> bb;}"
        )

Error thrown: NetworkXError: The node t is not in the graph.
If instead you pass a list for treatment and outcome it works, but will then fail when estimating the effect. As a work around you can pass a list during construction then override the attributes after construction:
import pandas as pd
import dowhy
from dowhy.do_why import CausalModel
z=[i for i in range(10)]
random.shuffle(z)
df = pd.DataFrame(data = {'zz': z, 'tt': range(0,10), 'bb': range(0,100,10)})
model=CausalModel(
        data = df,
        treatment=['tt'],
        outcome=['bb'],
        graph="digraph {zz -> tt;zz -> bb;tt -> bb;}"
        )
# workaround
model._treatment = 'tt'
model._outcome = 'bb'

identified_estimand = model.identify_effect()
print(identified_estimand)

model._treatment_name=''
causal_estimate = model.estimate_effect(identified_estimand,
        method_name="backdoor.propensity_score_matching")
print(causal_estimate)
print("Causal Estimate is " + str(causal_estimate.value))

Run on a google colaboratory instance with dowhy installed via:
!pip install -q git+https://github.com/Microsoft/dowhy.git
networkx version: 2.2
python: 3.6.7

bug fix on a PR!

recreated your test case. fix confirmed with this branch:
https://github.com/Microsoft/dowhy/pull/44/files
@amit-sharma please merge and resolve issue.

Thanks @akelleh Merging


Pattern production guidelines

Create production guidelines for the pattern exhibit images as well as suggested and required sections for

Going to close this one out due to inactivity!


[Regression] Materialized view with multiple indexes errors

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
Hi! Upon updating to dbt v1.7.14, all models materialized as "materialized_view" and including more than one index in its config fail with a syntax error. This did not happen in v1.7.13. The error looks like this:
15:36:06    Database Error in model int_test (models/intermediate/int_test.sql)
  syntax error at or near "create"
  LINE 13:   (foo)create  index if not exists

It looks like the multiple "create index" statements are being concatenated together incorrectly. I'm wondering if this is related.
Expected Behavior
I would expect materialized views with multiple configured indexes to build and run without error.
Steps To Reproduce
Model (int_test.sql):
{{
    config(
        materialized="materialized_view",
        indexes=[
            {"columns": ["foo"], "type": "btree"},
            {"columns": ["bar"], "type": "btree"},
        ],
    )
}}

SELECT 1 AS foo, 2 AS bar

Command: dbt run --select int_test
Output:
15:41:31  1 of 1 START sql materialized_view model intermediate.int_test ............. [RUN]
15:41:31  1 of 1 ERROR creating sql materialized_view model intermediate.int_test .... [ERROR in 0.06s]
15:41:31
15:41:31  Finished running 1 materialized_view model in 0 hours 0 minutes and 0.37 seconds (0.37s).
15:41:31
15:41:31  Completed with 1 error and 0 warnings:
15:41:31
15:41:31    Database Error in model int_test (models/intermediate/int_test.sql)
  syntax error at or near "create"
  LINE 13:   (foo)create  index if not exists
                  ^
  compiled Code at /opt/wg/.meltano/transformers/dbt/target/run/db/models/intermediate/int_test.sql
15:41:31
15:41:31  Done. PASS=0 WARN=0 ERROR=1 SKIP=0 TOTAL=1

Removing one or both of those indexes works just fine:
{{ config(materialized="materialized_view") }}

SELECT 1 AS foo, 2 AS bar

=>
15:43:57  1 of 1 START sql materialized_view model intermediate.int_test ............. [RUN]
15:43:57  1 of 1 OK created sql materialized_view model intermediate.int_test ........ [SELECT 1 in 0.17s]
15:43:57
15:43:57  Finished running 1 materialized_view model in 0 hours 0 minutes and 0.39 seconds (0.39s).
15:43:57
15:43:57  Completed successfully
15:43:57
15:43:57  Done. PASS=1 WARN=0 ERROR=0 SKIP=0 TOTAL=1

Relevant log output
No response
Environment
- OS: Ubuntu 20.04
- Python: 3.9.19
- dbt: 1.7.14

Which database adapter are you using with dbt?
postgres
Additional Context
No response

@bdewilde Thanks for the report!
I can confirm that this change likely caused the regression, because adding that ; back does seem to restore the previous behavior.
Following the reproduction case:
    create materialized view if not exists "jerco"."dbt_jcohen"."int_test" as

SELECT 1 AS foo, 2 AS bar;

    create  index if not exists
  "13008d29068d3f93577844cc147dd809"
  on "jerco"."dbt_jcohen"."int_test" using btree
  (foo);create  index if not exists
  "d9594d6bdc8ad05fa90f86119dd485f3"
  on "jerco"."dbt_jcohen"."int_test" using btree
  (bar);

I don't know if adding it back in exactly the same spot is right way to resolve this, versus somewhere else in the MV creation/update flow. Either way, we should:

Restore support for MVs with multiple indexes
Add a test to ensure it doesn't regress again

Note we have no tests for verifying this behavior one way or another in existence currently. The multiple index thing should cover this ; case.


[DOCFIX] Modify metric system docs

Merged build finished. Test PASSed.

@ZacBlanco @calvinjia PTAL, thanks!

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/7124/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/7128/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/7134/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/7143/
Test PASSed.

PR is overall LGTM, but if we are adding all of the different types of metrics I would like to see a description for each one

@ZacBlanco Removed the metrics that don't have detailed descriptions, PTAL

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/7187/
Test PASSed.

@calvinjia PTAL, thanks!

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/7192/
Test PASSed.

alluxio-bot, merge this please.

alluxio-bot, cherry-pick this to branch-2.1 please.


fixed residuals instead on first iteration

Hello,
I would like to start construction of boosting trees from some fixed (per sample) residuals .
How to do this in XGBoost?
Objective is binary:logistic
Thanks!
Sergey.

new questions are now encouraged at https://discuss.xgboost.ai/ To answer your question, you can use base_margin input to the booster


When you tap the eye, title text is white

how to make it so when you view text its black, titles etc are white here.

This is related to your CSS.


using filemin in "webmin via httpd"

Hi,
I (am required to) use Webmin via httpd so that I access via "http://myserver.url/webmin/". This gives the issue that when uploading a file using your wonderful tool (thank you E6) I receive a redirect to an invalid url for "uptracker.cgi" - it is looking for "http://myserver.url/uptracker.cgi" when it "should" be looking for "http://myserver.url/webmin/uptracker.cgi"
The file(s) upload - as long as we leave the "broken" redirect page open until the upload is complete - so there is one workaround :)
Kind regards,
Harrywwc
p.s. and again, a million thanks for this tool - so much "better" than the Java based clunker that really should have been retired ages ago!

OK - sorry - not "your" problem - it seems to be an issue with Webmin itself - as that is where the "uptracker.cgi" file resides.
Now to figure it out - sorry for the ID10T moment ;)
.h

quick update - I am using 0.9.2 (forgot top mention that ;)
I have commented out the onsubmit javascript call to "uptracker" in both of the dialogs.html files in the unauthenticated/templates directory
I will continue (all be it more slowly) looking at why the webmin uptracker.cgi file isn't being found by those html files.
Did I say how much I like this tool? :)
Kind regards,
Harry
(oh, my server is CentOS 6.6 - all up-to-date as of this morning)

I'll look into it. But I think it is more Webmin issue, cause it is really hard to make it work from subfolder.
Navigate to http://yourserver.url/webmin/updown/ and see if uptracker works there.


Registering an Event twice causes events to get lost for some systems

https://github.com/bevyengine/bevy/blob/fee7a26137689248733b64ce84f17316921c2ab5/crates/bevy_app/src/app.rs#L621
When calling .add_event::<SomeResource>() twice for the same resource, e.g. from different Plugins, sometimes some systems no longer receive events.
The reason for this is in the App::add_event I think
init_resource on an already registered resource is a no-op, but add_system_to_stage is also called twice, causing the system to clear & swap buffers multiple times.
The following Code would alleviate this, I think (still reproducing):
    pub fn add_event<T>(&mut self) -> &mut Self
    where
        T: Resource,
    {
        if !self.world.contains_resource::<Events<T>>() {
            self.init_resource::<Events<T>>()
                .add_system_to_stage(CoreStage::First, Events::<T>::update_system);
        }
        self
    }

Is this sensible?
I don't know how to make a test case for this - it just happens sporadically after all. Is one needed?

IMO we should panic with a clear warning, rather than silently succeeding here. Generally when this happens, it's a copy-paste / code migration error.
P.S.
Thoughs: I think it is reasonable that multiple distant pieces of Code need the same event to be registered. However they could depend on the same Plugin which registers it, making it that other Plugins responsibility.
If I am not mistaken, Plugins can be registered twice though too, right? I vaguely recall there being an Issue discussing this, but I can't find it.

If I am not mistaken, Plugins can be registered twice too though, right? I vaguely recall there being an Issue discussing this, but I can't find it.

Ah right: yes. Typically, this will be done with a generic type parameter, to create related but distinct behavior.
Okay, alright, I think I like your proposed solution then. Open a PR?

Generally speaking, this is part of #1255: the fact that we're using an unstructured approach to plugins using the builder pattern makes this flavor of error pop up all over the place.

Open a PR

:+1: will do


Missing fastcore for tests at CI

Fixed in
https://github.com/kdorichev/text2speech/commit/6fe69ae5ca12c8fe5a0b826880ec627a5198fa0c
https://github.com/kdorichev/text2speech/commit/aa4529698a70b012a048c4f3be31b0aefd8c0666
https://github.com/kdorichev/text2speech/commit/76021417e8b93d6ac7bc29e8d1b77816b2a4be03


check file content md5

Summary
add md5 check on local file and remote file
Related Issues
#103  add content-md5 check on local file and remote file

/lgtm
/approve


Merge master branch to prTesting1_202011051914 branch

Docs Build status updates of commit 7a5155c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Not able to connect to sponge server behind BungeeCord proxy

It's not able to connect to a sponge server which is behind a BungeeCord proxy. The sponge server does not give out any information of a try of connection to the server.
There are no error-messages, the player simply does not connect to the server. The bungeecord-proxy says, that the player connected but also shows that he disconnected in the next message. There are no logs at the sponge server.
Sponge-Version: sponge-1.8-1487-2.1DEV-523
BungeeCord-Version: Build 1076

I'm unable to reproduce it. Could you provide your configs (Bungee config.yml and Sponge server.properties)?

several staff members have managed to reproduce it

Make sure ip forwarding is disabled.

It works with disabled ip-forwarding.

Closing since this is a duplicate of #65


wrong link from beta ETMoses to beta ETM

When you want to go from the beta ETMoses to the beta ETM to make a new LES, it doesn't work:

The link is wrong, it should be
https://beta-pro.energytransitionmodel.com
instead of
https//beta-pro.energytransitionmodel.com
( a colon is missing after https)

Do you remember where you found this link?

This link opens when I click on the green bar 'Go to the energy tranistion model' at https://beta-moses.energytransitionmodel.com/welcome


Documentation renders properly locally, but not on ReadTheDocs

For some reason, docs render perfectly when built locally, but break completely when loaded onto ReadTheDocs.

Partly fixed in 49f5b17, but the docs for the Abstract Base Classes are still broken.

Partly fixed in 49f5b17, but the docs for the Abstract Base Classes are still broken.

Closed by 49f5b17.

Closed by 49f5b17.


[Event Request] Codeunit 99000845 Reservation Management - OnBeforeDeleteItemTrackingConfirm

Hi Team,
In codeunit 99000845 we need possibility to replace and avoid using standard code. Having event with handling in the beginning of procedure DeleteItemTrackingConfirm, would be a perfect solution :

[IntegrationEvent(true, false)]
local procedure OnBeforeDeleteItemTrackingConfirm(var CalcReservEntry2: Record "Reservation Entry";var IsHandled: Boolean)

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


The renamed app directories should not get an .app extension

The app directories are currently renamed to x64.app and arm64.app. But .app has a special meaning in macOS, causing these directories to appear as a corrupt application. Perhaps it is safer to rename them to app-x64 and app-arm64 or something similar.

Ah good call, tbh I've been testing this with an app that uses ASARs so the path for non-asar apps isn't well tested at all

Fixed in 82acb6f


1.0.16_crab version of Use system environment for gfal2 stageout

Oops, didn't mean to merge into master. My bad, closing.


WeightedMeanReport bugs

[ ] the "sort by" parameter name is given as the "WeightedMeanName" instead of the "Calc from" parameter

[ ] If the report csv is open and you try and append (or create a new one) to it you get the following message "Report file does not exist".  This isn't true, it does exist you just can't get at it.  This message box also comes up (as you would expect it to) if you try and append but a new file doesn't yet exist.

[ ] This is sort of related to the above point: it is currently not possible to see if a report exists for a given sample before you choose "New" or "Append".  If there was an existing one and you chose "New", the existing one gets wiped out and replaced by the new one.  I don't have a proposed solution off the top of my head, but maybe the simplest solution is not to write the file automatically but instead open window where the user creates a new csv or appends?  We can discuss possible ways around this on Monday, just flagging this here for now.

1 - not sure what you are talking about re: "sort by" issue
2 - that is a "windows" issue - but fixable
3 - your idea is probably the best as folks are used to that scenario in general

WeightedMeanReportForSample_10493.zip
The attached zip files shows what I mean.  This is the output of some weighted mean AGES but you can see that the column labelled WeightedMeanName is populated by "SpotIndex" (which was the sort by parameter), not the Age type.
If we implement the idea from -3, -2 becomes mostly moot so might not be worth the trouble to fix.

Fixed in release v1.4.9


Data docs - https://github.com/G-Research/armada/issues/203

Add a persistent volume/persistent volume claim example to our example docs.
Add an example that uses pvc/pv according to https://github.com/G-Research/armada/issues/203.

We will go ahead and close this PR.  Issue has not gotten clarity and it doesn't seem to be of great interest.


Test script which don't use 'make' command

Can I write test integration script for the environment which can't use 'make' command?
I want to write it by simple Python or travis CI (If you want).

Sure! Travis CI seems very cool for me. I will follow your implementation for Travis CI.


PDB signature fixes

This commit fixes two issues with the PDB signature generation:

the age field needs to be expressed as a hex number, not decimal
the age field is actually the one from the DBI stream, not the PDB stream

To see the first one, compile a project about 10 times, then use symstore.exe to store the PDB in a symbol store. Note that the signature ends with "...a", not with "...10".
To see the second one, you need to modify the PDB after it is being created by the linker. In our build system, we do this by invoking PDBSTR. This tool embeds a lookup-table inside the PDB, which enables source-level debugging on any machine, automatically. When it embeds the lookup table inside the PDB, the PDB age gets incremented. However, symstore.exe still uses the linker-generated age. Also, when VisualStudio or WinDBG search for the PDB, they still search for the original age. Hence, the age that needs to be retrieved is not the one specified in the PDB header stream, but the one in the DBI header stream (stream #3).
The two remaining commits introduce multi-page reads for the streams (since the DBI stream can be quiet large, hence the page table could span multiple pages) and also a fallback to the PDB age, just in case the PDB does not have a DBI header at all (only saw this with vc140.pdb).

Cool rbosa!
I'm on the road right now, but I hope I can look into this next week when I'm back home.

The changes look good, I have merged them to the master brunch.
However I need to add regression tests for new code. I have a pdb file with age > 10, however I don't know how to produce a file where age differ between PDB and DBI streams. Can you share your file?
Also, if you happen to have a file where multi-page reads are required and you can share, it would be great.
And, thanks for the patch!

I've added two more changes to make TravisCI build properly.
In regards to modifying a PDB to see the other changes, you can use the PDBSTR.EXE utility. I found mine in the %WindowsSDKDir%\Debuggers\x64\srcsrv folder. Create a text file mystream.txt and then invoke it like this:
pdbstr.exe -w -p:PDBFILE -i:mystream.txt -s:srcsrv

This should modify the PDBFILE in place, by embedding the text file as a new stream. It increments the 'age' in the PDB header, but not the DBG header.
As far as the multi-page reads goes I forgot which file required it. I would assume any larger project should create a DBG section that's big enough to require the multi-page read. But I don't have one to share freely, sorry.

I have now added regression tests for the bugs that you have fixed. Sorry for it taking so long time.
Regarding vc140.pdb file, it seems that symstore.exe just skips appending age to the hash string. I have changes symstore to behave in the simular way.
About you commits that fixes errors on travis CI, I fixed these errors earlier, so there is no need to merge them.
Anyways, I'm closing this PR as all fixes are now on master. I'm planning to make a new release with the your fixes soon(TM).
Thanks for the bug fixes!

Woot!

On Sep 21, 2016, at 23:25, elmirjagudin<EMAIL_ADDRESS>wrote:
Closed #1.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


feat(core): add package for core data types and their methods

This PR include infrastructure code necessary to start refactoring the existing code and prepare for #22
It contains the Provider struct, its associated data types and their methods.

I have never really looked into the module package. But yes, it would totally make sense to move the Module struct as well. Maybe once we'll start refactoring :)


Verify Meshnet services using this container

Container platforms mostly use overlay networks to enable the network abstraction layer. Since Meshnet is a service relying and depending on networking, and is not originally intended to be run in a container, it's possible not all Meshnet services function as expected.
Routing through this container using the Meshnet network is working fine, this is my original use-case, to use a Meshnet node/peer as an exit node like any traditional VPN.
Local network access works as expected. All local IP ranges (RFC 1918) seem to be available. Blocking this access will initiate firewall rules to block all non-internet routable IP ranges. The fact that NordVPN runs in a container does not change anything about this functionality.
To be tested:

Does the filesharing function work? Is this even something that should be enabled/used within a container?
Does the Remote Access service work? According to the docs this allows Pings and other direct connected service access.

Updated with new tests, local network access and blocking local access works as expected.


use the same groupname as other in secret creation

Signed-off-by: Chmouel Boudjnah<EMAIL_ADDRESS>
Changes

Submitter Checklist

[ ] ♽  Run make test lint before submitting a PR (ie: with pre-commit, no need to waste CPU cycle on CI
[ ] 📖 If you are adding a user facing feature or make a change of the behavior, please verify that you have documented it
[ ] 🧪 100% coverage is not a target but most of the time we would rather have a unit test if you make a code change.
[ ] 🎁 If that's something that is possible to do please ensure to check if we can add a e2e test.
[ ] 🔎 If there is a flakiness in the CI tests then don't necessary ignore it, better get the flakyness fixed before merging or if that's not possible there is a good reason to bypass it. (token rate limitation may be a good reason to skip).

Codecov Report

Merging #1131 (89dca89) into main (0c4a8af) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #1131      +/-   ##
==========================================
+ Coverage   63.00%   63.02%   +0.01%
==========================================
  Files         106      106
  Lines        6380     6382       +2
==========================================
+ Hits         4020     4022       +2
  Misses       1975     1975
  Partials      385      385

Impacted Files
Coverage Δ

pkg/secrets/basic_auth.go
94.73% <100.00%> (ø)

pkg/acl/acl.go
100.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.