#1651: fix memory exhaustion in find-missing-issues#1776
Open
VasilevNStas wants to merge 3 commits into
Open
Conversation
…agination overhead
…aming iteration to avoid memory exhaustion
…t unrelated code-was-reviewed per_page change
Contributor
Author
|
@yegor256 plz review |
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
1 participant
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.
Replaces the array-based missing issue detection in
find-missing-issues.rbwith aSet-based streaming iteration to avoid memory exhaustion on repositories with sparse issue numbers.Previously built
must = (min..max).to_aandmissing = must - issues, constructing large arrays for gaps. Now iterates the range and checks membership viaSet#include?.Also fixes the log message variables to comply with
Elegant/GoodVariableName(no underscores).Closes #1651