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
if I load https://viz.covid19forecasthub.org/ and then rapidly navigate backwards in time, I can sometimes get to a place where the forecasts look "weird" (screenshot attached).
My best guess about why is that multiple data fetch requests were issued and then resolved out of order. For instance, in this plot I think the displayed forecasts are from an earlier as of date than the displayed "as of truth data", and that's resulting in the graphic glitches. It seems like we might want to implement a check around here that verifies that the data fetched in the Promise that is now resolving match the current settings in the app state before updating the plot. That is, we only update the aspects of the plot based on this data fetch if the app state didn't change between the time the data fetch was issued and the time it resolved.
The text was updated successfully, but these errors were encountered:
@elray1 Any tips for recreating this consistently? I haven't had much luck. Is there a particular pattern of <- and -> arrows? Is it more likely to happen when moving left into non-cached states? Thanks.
I am still getting this kind of thing occasionally if I just hold down the left arrow key; no specific guidance.
Separately, but I think essentially due to the same fundamental issue about queries not necessarily being executed and returning results in a reliable order, I got to the following plot where the current truth line is for a different location than the forecasts and the "as of truth". To get here, I gave the "Unit" drop-down menu focus and then used the left/right arrow keys to simultaneously navigate across locations and time points.
if I load https://viz.covid19forecasthub.org/ and then rapidly navigate backwards in time, I can sometimes get to a place where the forecasts look "weird" (screenshot attached).
My best guess about why is that multiple data fetch requests were issued and then resolved out of order. For instance, in this plot I think the displayed forecasts are from an earlier as of date than the displayed "as of truth data", and that's resulting in the graphic glitches. It seems like we might want to implement a check around here that verifies that the data fetched in the Promise that is now resolving match the current settings in the app state before updating the plot. That is, we only update the aspects of the plot based on this data fetch if the app state didn't change between the time the data fetch was issued and the time it resolved.
The text was updated successfully, but these errors were encountered: