feat(alert): add option to use custom socket #1219
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds the ability to pass in a custom socket for the AlertListener.
In some cases attempting to use the AlertListener, will fail with the message
getsockaddrarg: bad family
. I believe this is due to using IPv6 on Linux hosts, but I cannot confirm. Adding the ability to use a custom socket, would allow the developer to create their own socket to use in this event.Type of change
Please delete options that are not relevant.
Checklist: