Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Contents should not regress even with a spotty network connection #833

Open
1fish2 opened this issue Mar 28, 2017 · 2 comments
Open

Contents should not regress even with a spotty network connection #833

1fish2 opened this issue Mar 28, 2017 · 2 comments
Labels

Comments

@1fish2
Copy link
Contributor

1fish2 commented Mar 28, 2017

The cellular network was overloaded at the Glacier Peak Event -- enough signal bars but very poor data throughput. [In the event survey, I suggested that FIRST ask the cellular providers to set up COWS (Cell sites On Wheels) for all FRC events. Let's suggest this early and often.]

People can understand not getting updates, but the app displayed content regressions such as:

  • Go back to the event's Teams screen and see an empty list or a short list of teams. When it can't fetch new data, why does it lose earlier data? If a network response gets cut short, doesn't the HTTP library indicate that?
  • Go back to the event's Rankings screen and see smaller W-L-T counts than earlier. I took this screenshot after Quarter Finals when it claimed the top qual scores as (1-0-0)!

screenshot_20170326-150225

@phil-lopreiato
Copy link
Member

Man, I have no idea why this could happen. But it's definitely not good...

I'll see if I can reproduce this weekend somehow and see what's going on

@TheBassett
Copy link

TheBassett commented Apr 1, 2017

I saw this issue today as well. I was able to replicate it once on purpose but then the next time around it only was partially replicated.

My process:

  1. Viewed a regionals rankings at some point in the day
  2. Viewed same regionals rankings later to see the updates
  3. Turned off mobile data (to try to save battery) then turned the screen off/put the phone to sleep.
  4. When I turned on the screen the rankings had reverted back to the old data I saw earlier in the day.
  5. When I turned mobile data back on and reloaded I had the correct rankings.
    Note: Network/UI bug #828 is still present so you must reload from the list of events page instead of the single event/event breakdown page (atleast that was my experience).

I was able to repeat these steps for the full effect one other time. Sadly, on the third time, the error didn't appear the same - I was still able to see the old rankings blip up but then they got replaced with the new ones immediately.

Hope this helps!

Original Rankings:
realrankings

Regression Rankings:
fakenewrankings

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants