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
The alias unique service has a check to see if an alias matches an existing route.
That alone is fine. But the problem is that the alias manager then just retries with -0, which in most cases, matches the route again. Then -1, and so on.
This results in an endless loop.
5bca622 is a workaround that at least throws an exception. But I'm not sure if the route check like this is actually correct and should be there. That should possibly be checked separately and a match should just abort.
The text was updated successfully, but these errors were encountered:
The alias unique service has a check to see if an alias matches an existing route.
That alone is fine. But the problem is that the alias manager then just retries with -0, which in most cases, matches the route again. Then -1, and so on.
This results in an endless loop.
5bca622 is a workaround that at least throws an exception. But I'm not sure if the route check like this is actually correct and should be there. That should possibly be checked separately and a match should just abort.
The text was updated successfully, but these errors were encountered: