-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
xdsclient: populate error details for NACK #3975
Conversation
) | ||
switch update := u.(type) { | ||
case *watchAction: | ||
target, rType, version, nonce = t.processWatchInfo(update) | ||
case *ackAction: | ||
target, rType, version, nonce, send = t.processAckInfo(update, stream) | ||
target, rType, version, nonce, errMsg, send = t.processAckInfo(update, stream) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why does processAckInfo
have to return the errMsg
. Why can't we use it directly here? It is available in update
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right. This is unnecessary, and processAckInfo
cannot change it anyway. Done.
send bool | ||
target []string | ||
rType ResourceType | ||
version, nonce, errMsg string |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: We might as well get rid of errMsg
and use update.errMsg
directly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a switch: case
. Only ackAction
has the errMsg
field.
fixes #3969