<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/466d39f90c28410eb031941a636f7565&quot; frameborder=&quot;0&quot; width=&quot;1664&quot; height=&quot;1248&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1248</height><width>1664</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1248</thumbnail_height><thumbnail_width>1664</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/466d39f90c28410eb031941a636f7565-00001.gif</thumbnail_url><duration>481.83333333333445</duration><title>Flake: cannot-join-two-saved-questions</title><description>In this Loom, I delve into the issue of schema inconsistencies that occur when running tests. I explore the differences between passing and failing cases, highlighting the pattern of database, schema, and table rendering. I investigate the constructor and the logic around hydrating active steps, specifically focusing on the skip tests and load step data functions. I also examine the timing of schema loading and the creation of entities, uncovering a potential race condition. Finally, I discuss the update questions logic and its connection to the creation of the schema entity. Watch this Loom to understand the root cause of the schema inconsistencies and the potential impact on the data selector component. No action is requested from viewers.</description></oembed>