Testing reveals that this is not fixed yet. Running the PRF in debug mode I can see an abort is called during addReleaseTarball(). The code has a loop that duplicates the old hasReleaseFile() method to end early if there is a binary associated with the release.
We want to remove the whole loop because hasReleaseFile() makes the decision; addReleaseTarball() should do as it is told. This will also make adding files faster since the the loops not needed.
Testing reveals that this is not fixed yet. Running the PRF in debug mode I can see an abort is called during addReleaseTarba ll(). The code has a loop that duplicates the old hasReleaseFile() method to end early if there is a binary associated with the release.
We want to remove the whole loop because hasReleaseFile() makes the decision; addReleaseTarball() should do as it is told. This will also make adding files faster since the the loops not needed.