-
Notifications
You must be signed in to change notification settings - Fork 0
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
fix: middleware message handling #28
base: master
Are you sure you want to change the base?
Conversation
pkg/middleware/unimplemented.go
Outdated
_, err = (*b.client).Handle(context.Background(), req) | ||
return nil, err | ||
klog.V(0).Info("processing next middleware") | ||
ctxTimeout, cancelTimeout := context.WithTimeout(context.Background(), 12*time.Second) |
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.
Shouldn't we add the retry config here too?
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.
default retry policy is added when creating the client for the next middleware in this file, you mean that?
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.
Now I've seen the defaultRetryPolicy variable use, thanks :-)
klog.Errorf("Failed to remove socket: %v", err) | ||
} | ||
|
||
err = os.MkdirAll(filepath.Dir(socket), 0775) |
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.
Where is the socket folder created now?
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.
we don't need to, do we?
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.
I think so, you don't know the socket path you are receiving, so, How do you know it is created?
This PR aims to fix some issues related to middleware message handling:
Additionally: