Under certain conditions doOptimizeAt in _internalUnpackBucket will swap with a sort without checking if the sort has an internal limit. Since we optimize the pipeline from left to right, this does not cause any issues. However it's possible this could cause a bug in the future where we provide more results to the user than expected by accidentally pushing the limit back.