{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/9cf9602e2c2e4ac1a449055b6e36917b\" frameborder=\"0\" width=\"1662\" height=\"1246\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1246,"width":1662,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1246,"thumbnail_width":1662,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/9cf9602e2c2e4ac1a449055b6e36917b-40bb480bc2ec82a7.gif","duration":254.305,"title":"Fixing Discourse Sync Initial Missing Content","description":"This Loom describes a startup patch to ensure missing discourse contents and concepts are “absurded” before normal time-based syncing resumes. The author explains that the previous behavior sometimes never “absurded” all non-atomic concepts after updating content, so they added a global initial sync that brute-forces missing items by intersecting all new nodes with existing content IDs and concept IDs from the database. In the CreatorUpdateDiscourseEmbedding function, they record the initial sync status at the start and set it to false only if the first sync finishes successfully. A demo deletes three concept rows, reloads to force initial sync, and shows the system upserting the missing concept and content entries, after which the subsequent query finds nothing left."}