-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TimSort, first fix values, then sort #2781
Merged
Merged
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
Codecov Report
@@ Coverage Diff @@
## master #2781 +/- ##
=========================================
+ Coverage 6.39% 6.42% +0.02%
=========================================
Files 294 297 +3
Lines 29443 29721 +278
Branches 4252 4286 +34
=========================================
+ Hits 1884 1909 +25
- Misses 27272 27528 +256
+ Partials 287 284 -3
|
AndyScherzinger
added a commit
that referenced
this pull request
Jul 4, 2018
Backport of #2781: TimSort, first fix values, then sort
Signed-off-by: tobiasKaminsky <[email protected]>
Signed-off-by: tobiasKaminsky <[email protected]>
AndyScherzinger
force-pushed
the
timSortWithFixedValues
branch
from
July 12, 2018 15:45
87bd3e9
to
094d47b
Compare
Signed-off-by: tobiasKaminsky <[email protected]>
Signed-off-by: tobiasKaminsky <[email protected]>
Lint
FindBugs (new)
FindBugs (master)
|
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.
TimSort is crashing because values (e.g. upload status) is changing while sorting.
Therefore the idea is to "fix" these values for sorting.
Drawback is that it can happen that sorting is already outdated, once sorting is done.
But we refresh after each upload and also a manual refresh can be triggered.
This is currently #1 bug on google play console.
For developing, I set each value of OCUpload to random and had a crash on nearly every sorting/refresh.
With this enhancement, I had no crash at all, although every value changed at any time.
We are using these fixedValues only for sorting and read-only.
So a changing status, e.g. because upload failed, will still be reflected on next sort.
Signed-off-by: tobiasKaminsky [email protected]