-
Notifications
You must be signed in to change notification settings - Fork 91
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
Collect now: doesn't always update (v2) #272
Comments
dasgarner
added a commit
to dasgarner/xibo-dotnetclient
that referenced
this issue
Nov 17, 2022
dasgarner
changed the title
Collect now: doesn't always update
Collect now: doesn't always update (v2)
Nov 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We started to notice some strange behaviour with the collect now functionality, particularly when creating a new layout, scheduling it and wanting to have that reflected on the display immediately.
We noticed that the XMR message was being pushed, but the player did not always update as expected.
The root cause of this is a race case between register and rf/schedule calls. This only started being an issue when we introduced the RF/Schedule checksums on the register return, which skip rf/schedule if the cache has not changed.
Because register/rf and schedule all get woken up at the same time, then rf/schedule are often analysed and ignored before the cache checksums have updated on schedule.
This is not a problem in v3
The text was updated successfully, but these errors were encountered: