bugfix: move MaxInFlightLimit handler chain after RequestClientComponent #451
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.
Signed-off-by: SataQiu shidaqiu2018@gmail.com
What type of PR is this?
/kind bug
What this PR does / why we need it:
MaxInFlightLimit
wants to show the client component, but the client component info is available only afterRequestClientComponent
chain executed.openyurt/pkg/yurthub/proxy/util/util.go
Line 235 in b7bef6d
openyurt/pkg/yurthub/util/util.go
Line 131 in b7bef6d
This PR move
MaxInFlightLimit
handler chain afterRequestClientComponent
.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
/assign @rambohe-ch
Does this PR introduce a user-facing change?
other Note