You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we get this (when the user has not visited for a while) -
The drop-off there on 342 is because of an incomplete session. We should rather track to make sure we have rewards for all era-ends. (Bit tricky generally, since not all epoch ends are era ends as per current.)
So probably need to add a flag to make sure it is indeed session-ending. If not, discard.
Currently we always re-load at least a full era, which is wasteful on each load - and well, if you stay . away fro 2 days, you have issues.
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.
Currently we get this (when the user has not visited for a while) -
The drop-off there on 342 is because of an incomplete session. We should rather track to make sure we have rewards for all era-ends. (Bit tricky generally, since not all epoch ends are era ends as per current.)
So probably need to add a flag to make sure it is indeed session-ending. If not, discard.
Currently we always re-load at least a full era, which is wasteful on each load - and well, if you stay . away fro 2 days, you have issues.
The text was updated successfully, but these errors were encountered: