You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An external library that depends on a listed library will be assigned order 0. This leads to wrong update order. It is easy to fix, by adding the library to the extract list. Opened this issue to figure out whether something should be done to prevent this.
The text was updated successfully, but these errors were encountered:
The dependency info could be used for comparing the ecosystem against crates.io. This information is used to detect updates, so errors caused by holes is because the dependency information has holes. The recommended action to add to extract list makes only sense if the extract list is used to generate the dependency info.
When the dependency info does not list a library at top level, it could be a hole, but it usually is not.
!listed_at_top_level, ?!hole.
A library listed at top level can not be a hole.
listed_at_top_level, !hole.
If a library does not have any dependencies, then it is not a hole.
no_dependencies, !hole.
Adding a package to the dependency information might introduce holes, but usually it does not:
add_package, ?!introduce_holes.
Removing a package from the dependency information does not introduce holes.
remove_package, !introduce_holes.
A package can only introduce holes with less depth than itself. If there is no other library with less depth then it can not introduce holes.
An external library that depends on a listed library will be assigned order 0. This leads to wrong update order. It is easy to fix, by adding the library to the extract list. Opened this issue to figure out whether something should be done to prevent this.
The text was updated successfully, but these errors were encountered: