-
Notifications
You must be signed in to change notification settings - Fork 574
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
Fix broken downtime comment sync #10000
base: master
Are you sure you want to change the base?
Conversation
Quick question: would this also fix the following issue: |
It would be very helpful to get an answer to this. |
Hi, we don't know for sure whether this will fix #10078 as we still haven't identified exactly what is going wrong there, other than something is not working as expected. It's unlikely that this PR will fix #10078, but we can't tell you for sure until the cause for #10078 is identified. |
@yhabteab When will this request be completed? Is there a timeline? |
e3c289f
to
78095b8
Compare
cb4fe57
to
eb97676
Compare
I believe similar problems will still exist for other types where there's no |
A complete list of the navigable aka
|
78095b8
to
6effb4a
Compare
6effb4a
to
687013c
Compare
Another list of non-navigable dependencies :):
|
687013c
to
f8df6b4
Compare
All objects must be synced sorted by their load dependency. Otherwise, downtimes and/or comments might get synced before their respective Checkables, which will result in comments and downtimes being ignored by the other endpoint since it does not yet know about their checkables. Given that the runtime config updates event does not trigger a reload on the remote endpoint, these objects won't be synced again until the next reload.
After master2 reload:
closes #7786
closes #9873
TODO