[Cache] Don't use LazyProxyTrait in redis proxies #57326
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
945ad70 to
b4f05ea
Compare
b4f05ea to
7fc68c9
Compare
xabbuh
added a commit
that referenced
this pull request
Jul 17, 2024
…bbuh) This PR was merged into the 7.2 branch. Discussion ---------- [Cache] do not use LazyProxyTrait in RelayProxyTrait | Q | A | ------------- | --- | Branch? | 7.2 | Bug fix? | no | New feature? | no | Deprecations? | no | Issues | | License | MIT fixes tests after merging #57723 up into the `7.2` branch by taking #57326 into account Commits ------- a0a0867 do not use LazyProxyTrait in RelayProxyTrait
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Making things a bit simpler.
Forwarding dynamic properties to the real instance is the only benefit of using LazyProxyTrait here, and this has no use cases.