{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/9e3bfa9b4a7f4fc681284bc4002a91a8\" frameborder=\"0\" width=\"1280\" height=\"960\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":960,"width":1280,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":960,"thumbnail_width":1280,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/9e3bfa9b4a7f4fc681284bc4002a91a8-00001.gif","duration":117.33631011599998,"title":"prodigy dupes","description":"In this video, I express my gratitude to Vincent and Ryan for their assistance in reviewing my work. Despite implementing their suggestions, I am still encountering the same issue. I made some additional changes, such as adding \"overwrite true\" to the get stream call and fixing a typo in the JSON structure. However, I am puzzled by the fact that the machine runs twice in the logs. Moving on to Prodigy, there are now only 58 rows, and the task has become quite messy. I showcase the row counter and demonstrate how it fluctuates. Thank you for watching!"}