ttf-noto-sans is caused by the following errors in petgraph:
error[E0034]: multiple applicable items in scope
--> /Users/jdm/.cargo/registry/src/github.com-1ecc6299db9ec823/petgraph-0.2.9/src/graph.rs:421:17
|
421 | assert!(Ix::max().index() == !0 || NodeIndex::end() != node_idx);
| ^^^^^^^ multiple `max` found
|
note: candidate #1 is defined in the trait `graph::IndexType`
--> /Users/jdm/.cargo/registry/src/github.com-1ecc6299db9ec823/petgraph-0.2.9/src/graph.rs:31:5
|
31 | fn max() -> Self;
| ^^^^^^^^^^^^^^^^^
= help: to disambiguate the method call, write `graph::IndexType::max(...)` instead
note: candidate #2 is defined in the trait `std::cmp::Ord`
= help: to disambiguate the method call, write `std::cmp::Ord::max(...)` instead
error[E0034]: multiple applicable items in scope
--> /Users/jdm/.cargo/registry/src/github.com-1ecc6299db9ec823/petgraph-0.2.9/src/graph.rs:458:17
|
458 | assert!(Ix::max().index() == !0 || EdgeIndex::end() != edge_idx);
| ^^^^^^^ multiple `max` found
|
note: candidate #1 is defined in the trait `graph::IndexType`
--> /Users/jdm/.cargo/registry/src/github.com-1ecc6299db9ec823/petgraph-0.2.9/src/graph.rs:31:5
|
31 | fn max() -> Self;
| ^^^^^^^^^^^^^^^^^
= help: to disambiguate the method call, write `graph::IndexType::max(...)` instead
note: candidate #2 is defined in the trait `std::cmp::Ord`
= help: to disambiguate the method call, write `std::cmp::Ord::max(...)` instead
Since petgraph has 23 dependent crates, this suggests that this may be a significant source of the regressions. This has already been fixed in the most recent release of petgraph: https://github.com/bluss/petgraph/pull/154