Skip to content
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 SIGSEGV when no best route is found. (backport #702) #707

Merged
merged 2 commits into from
Apr 16, 2021

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Apr 16, 2021

This is an automatic backport of pull request #702 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.io/

In some case there is no a best route, and no source route can be assigned.
This fix set source with the address in the first route found in the route table
or 0.0.0.0 in case an empty route table.

(cherry picked from commit ad9499b)
(cherry picked from commit f90f089)
@mergify mergify bot requested a review from a team as a code owner April 16, 2021 08:58
@jjnicola jjnicola merged commit 101164a into master Apr 16, 2021
@jjnicola jjnicola deleted the mergify/bp/master/pr-702 branch April 16, 2021 10:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant