Submitted by hash, also found by lanrebayode77 and novamanbg
Invoking manualStopEmissionsFor can cause the user to miss out on rewards from vaults even after the user becomes eligible.
If lastEligibleStatus and isCurrentlyEligible returns true, only the balance of the specific vault is updated. The idea is that whenever both these are true, all the other balances would have already been updated to the current value and hence need not be re-queried again.
But this assumption is broken when manualStopEmissionsFor is called which will set the balance corresponding to each vault as 0:
In this case, if an users vault position update makes the user eligible for rewards, only that specific vault associated debt will be earning rewards and all the other vault balances wont be updated.
The lastEligibleStatus check can be removed or it can be handled alongside the manualStopEmissionsFor implementation.
amarcu (LoopFi) confirmed
