-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RouterCollisionPotentialReport Issues #891
Comments
Note that the error might be down to something I have changed in my branch |
That RouterCollisionPotentialReport needs a cfg 100% agree. |
The error however does not look like router_collision_potential_report fault but rather a GIGO router_tables_by_partition is saying that a link exists that the chip can not find |
report still uses n_keys_map |
@andrewgait notes: can we rename this report to change "protential" to "potential" |
Report has now been removed |
RouterCollisionPotentialReport appears to be enabled by default where it wasn't before, and has no config to stop this. When run with virtual chips, I seem to get the following error:
The text was updated successfully, but these errors were encountered: