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

server: if inserting bootstrap config entries fails don't silence the errors #6256

Merged
merged 1 commit into from
Aug 2, 2019

Conversation

rboyer
Copy link
Member

@rboyer rboyer commented Aug 1, 2019

No description provided.

@rboyer rboyer added this to the 1.6.0-rc1 milestone Aug 1, 2019
@rboyer rboyer requested a review from a team August 1, 2019 02:22
@rboyer rboyer self-assigned this Aug 1, 2019
Copy link
Member

@banks banks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch.

For confused onlookers, our raft lib allows just a single interface{} to be returned as the value when a log is applied. If there are application-level errors (as opposed to raft/transport level errors) they manifest in a nil error but an error as the actual response value.

This PR fixes the handling so that if the response is an error type we return that as an error instead of ignoring it.

@rboyer rboyer merged commit 1d0efdc into release/1-6 Aug 2, 2019
@rboyer rboyer deleted the config-entry-bootstrap-errors branch August 2, 2019 04:08
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.

2 participants