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

Consistent error handling across *SubscribeAt functions #654

Merged
merged 1 commit into from
May 30, 2021

Conversation

milan-zededa
Copy link
Contributor

Opening PR with a commit from my colleague @eriknordmark which unifies error handling between addrSubscribeAt, linkSubscribeAt and routeSubscribeAt.
The behavior is that while error from Receive() closes the subscription, a notification with unexpected data is just skipped trough with error message sent over through the provided callback. (already done this way for addrSubscribeAt)

Signed-off-by: eriknordmark [email protected]

@aboch aboch merged commit f9d8f91 into vishvananda:master May 30, 2021
milan-zededa added a commit to milan-zededa/eve that referenced this pull request Oct 13, 2021
All changes in our fork of vishvananda/netlink have been accepted
and merged into the upstream:
- vishvananda/netlink#654
- vishvananda/netlink#659

Signed-off-by: Milan Lenco <[email protected]>
milan-zededa added a commit to milan-zededa/eve that referenced this pull request Oct 13, 2021
All changes in our fork of vishvananda/netlink have been accepted
and merged into the upstream:
- vishvananda/netlink#654
- vishvananda/netlink#659

Signed-off-by: Milan Lenco <[email protected]>
eriknordmark pushed a commit to lf-edge/eve that referenced this pull request Oct 15, 2021
All changes in our fork of vishvananda/netlink have been accepted
and merged into the upstream:
- vishvananda/netlink#654
- vishvananda/netlink#659

Signed-off-by: Milan Lenco <[email protected]>
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.

3 participants