fix: honor configured history limit in CoreProtect lookups#1
Merged
Technofied merged 1 commit intoMCCitiesNetwork:masterfrom Apr 9, 2026
Merged
fix: honor configured history limit in CoreProtect lookups#1Technofied merged 1 commit intoMCCitiesNetwork:masterfrom
Technofied merged 1 commit intoMCCitiesNetwork:masterfrom
Conversation
Member
|
LGTM |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Added synchronization so that the configured maximum limits would be enforced from plugin.getSettings().historyLimitDate, rather than defaulting to MAX_LOOKUP_TIME_SECONDS in all instances.