[1.8.x] clean history_record when endpoint unmatches [7584] #1006
Conversation
This file contains 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
|
Build status:
|
|
Failures on Mac are due to #954 not being backported to 1.8.x |
IkerLuengo
added a commit
that referenced
this pull request
Feb 13, 2020
This is a port of #1006 from 1.8.x Only a partial port is done, as the main issue was already corrected during a refactoring * Ensure persistence_guid_count_ is deleted when it reaches to zero to free memory * Change the condition to delete the records from count == 0 to count <= 0 for robustness
IkerLuengo
added a commit
that referenced
this pull request
Feb 13, 2020
This is a port of #1006 from 1.8.x Only a partial port is done, as the main issue was already corrected during a refactoring * Ensure persistence_guid_count_ is deleted when it reaches to zero to free memory * Change the condition to delete the records from count == 0 to count <= 0 for robustness
IkerLuengo
added a commit
that referenced
this pull request
Feb 14, 2020
This is a port of #1006 from 1.8.x Only a partial port is done, as the main issue was already corrected during a refactoring * Ensure persistence_guid_count_ is deleted when it reaches to zero to free memory * Change the condition to delete the records from count == 0 to count <= 0 for robustness
MiguelCompany
pushed a commit
that referenced
this pull request
Feb 14, 2020
This is a port of #1006 from 1.8.x Only a partial port is done, as the main issue was already corrected during a refactoring * Ensure persistence_guid_count_ is deleted when it reaches to zero to free memory * Change the condition to delete the records from count == 0 to count <= 0 for robustness
MiguelCompany
pushed a commit
that referenced
this pull request
Feb 14, 2020
This is a port of #1006 from 1.8.x Only a partial port is done, as the main issue was already corrected during a refactoring * Ensure persistence_guid_count_ is deleted when it reaches to zero to free memory * Change the condition to delete the records from count == 0 to count <= 0 for robustness
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.
No description provided.