-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
fix(router): traditional router could error with "invalid order function for sorting" #10514
Conversation
@sabertobihwy and @zhangzerui20, What are your thoughts on this alternate implementation? Perhaps we can check if we have other structures too where we add same route when not needed. |
c67bd35
to
73128e8
Compare
8e437d1
to
ed0ee53
Compare
ed0ee53
to
1b27e75
Compare
6936d38
to
7919b75
Compare
I reviewed this PR and understood the fix and it's great! |
I have tried some combinations locally with no problems. BTW, the idea of tried is to make
now this PR works well. |
7919b75
to
11507e8
Compare
@chronolaw / @sabertobihwy, feel free to approve if you think it is fine. |
11507e8
to
2c3b731
Compare
…on for sorting" ### Summary The same route may have been added multiple times to `routes_by_sources[<ip|port>]` or `routes_by_destionation[<ip|port>]` which lead to "invalid order function for sorting" when we tried to sort the routes. This fixes the issue. KAG-918 ### Issues Resolved Fix #10446 Closes #10470 Signed-off-by: Aapo Talvensaari <aapo.talvensaari@gmail.com>
2c3b731
to
04d5f65
Compare
…er_token_param_type (#10514) Co-authored-by: Michael Martin <flrgh@protonmail.com>
Summary
The same route may have been added multiple times to
routes_by_sources[<ip|port>]
orroutes_by_destination[<ip|port>]
which lead to "invalid order function for sorting" when we tried to sort the routes. There was also sorting issue when multiple routes sorted the same. This fixes the issue.KAG-918
Issues Resolved
Fix #10446
Close #10470