3 ms·
That’s what I thought originally, but there really shouldn’t have been much load (ignoring the load of downloading the app to begin with). There were fewer than
by maxlybbert 7y ago
That’s what I thought originally, but there really shouldn’t have been much load (ignoring the load of downloading the app to begin with). There were fewer than 2000 precincts, and each precinct had to upload around 100 bytes of data. That shouldn’t have been hard.
One news story I read quoted an error message about a “missing protocol.” I believe that the “coding error” was really a configuration error: somebody forgot to include https:// https:// in the web service URL. The app recorded the data, but couldn’t upload it.
Load testing would have found this, but so would a single integration test/smoke test.
- runawaybottle 7y agoMy thinking is they simply didn’t do any dry runs with possible simulated data (bad data, malformed data, partial data), they didn’t consider all the ways things can go wrong in real time. This is less about load testing but more about exception handling/fallbacks.
- maxlybbert 7y agoI definitely agree with you there.
- SyneRyder 7y agoThere's a screenshot of that "Unknown Protocol" error message in this Vice article: https://www.vice.com/en_ca/article/y3m33x/heres-the-shadow-inc-app-that-failed-in-iowa-last-night https://www.vice.com/en_ca/article/y3m33x/heres-the-shadow-i... It (seems to) occur while trying to access a "2nd Factor Authentication" page at auth0.com, and there's a cross through the padlock icon at the bottom of the window.
- maxlybbert 7y agoThank you for tracking that down and sharing it!