improve: GenericRetry does not provide mutable singleton instance #2934
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
This might easily result in unintended side effect if someone uses `DEFAULT` instance in one controller, changes some paramter; then uses the instance for an other controller, in that case the changed parameter will apply also for other controller what is quite unintuitive Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
|
added also issue for v6 to refactor: |
metacosm
approved these changes
Sep 8, 2025
xstefank
approved these changes
Sep 8, 2025
csviri
added a commit
that referenced
this pull request
Sep 24, 2025
csviri
added a commit
that referenced
this pull request
Oct 7, 2025
This was referenced Oct 10, 2025
Closed
csviri
added a commit
that referenced
this pull request
Oct 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This might easily result in unintended side effect if someone uses
DEFAULTinstance in one controller, changes some paramter; then uses the instance for an other controller, in that case the changed parameter will apply also for other controller what is quite unintuitive