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
It takes too long for the status to be reflected on the home screen.
Here's an example of a ping that timed out after 1 minute:
And this is what it looks like on the home screen after 10 minutes:
Ideally, these things would be updated in real-time, but I suspect that'd make the implementation too complicated for such an infrequent use case. So as a compromise I'd suggest to re-query the DB when the user goes back to the home screen, for example, after being on the ping screen.
The text was updated successfully, but these errors were encountered:
Closes#26Closes#28
Now the ping state and dates refresh every 10 seconds by themselves, to handle state changes like a day has passed, or it has expired.
It takes too long for the status to be reflected on the home screen.
Here's an example of a ping that timed out after 1 minute:
And this is what it looks like on the home screen after 10 minutes:
Ideally, these things would be updated in real-time, but I suspect that'd make the implementation too complicated for such an infrequent use case. So as a compromise I'd suggest to re-query the DB when the user goes back to the home screen, for example, after being on the ping screen.
The text was updated successfully, but these errors were encountered: