Propagate a better address error #3312
Labels
theme/operator-usability
Replaces UX. Anything related to making things easier for the practitioner
type/enhancement
Proposed improvement or new feature
The unit test cleanup in memberlist ended up burying the real error message if an address isn't available. For example, with some other listener on an address/port normally you'd get an "address already in use" type error, but instead you get this:
We need to propagate the underlying error.
The text was updated successfully, but these errors were encountered: