Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

notification API seems to be slightly 'ahead' of class summary API

See original GitHub issue

Observed behavior

Observed by @jonboiser during last week’s hack sessio:

report data was updated based on an incoming notification
refreshed the page, and data went back to previous state

Expected behavior

Notifications and class summary API should either be in sync, or at least the summary API should contain the most recent data – not the other way around.

User-facing consequences

Strange fluctuations in reports data

Errors and logs

…

Steps to reproduce

…

Context

0.12.0 beta 4

Issue Analytics

State:
Created 5 years ago
Comments:7 (7 by maintainers)

Top GitHub Comments

1reaction

jonboisercommented, Feb 13, 2019

It’s probably easiest to see this on a page like Reports > Lessons.

Go to Reports > Lessons and view all of the lessons
As a learner, start or complete one of the lessons
Shortly after, the relevant lesson will update in the “Progress” column. E.g. it will go from “3 of 12 completed” to “4 of 12 completed”, which should happen without a refresh because of an incoming notification.
Go to another page.
Go back to Reports > Lessons
The “Progress” column will have gone back to “3 of 12 completed”

0reactions

indirectlylitcommented, Feb 28, 2019

I’ve tested and confirmed that this issue has been addressed between beta 7 and now:

Behavior in beta 7 was that the class_summary_api incorrectly reported an in-progress content item as NotStarted. This caused the lesson in-progress state to revert back after navigation, which is when we currently refresh the class summary.
Behavior in current release branch is that in-progress content items are correctly reported