<transcript><audio_290>apparently the python was so so many jobs on the GI back and that it just just broke the whole website um that is not a mistake but like you know said it's a weird thing to say uh in in terms of actual mistakes I have made um</transcript><transcript><audio_291>hopefully like the the the good thing about mistakes as release managers that you can correct them and nobody sees them but some of the classic mistakes that I have made for instance that uh when when you finish like the release of a branch so let's say you're releasing</transcript><transcript><audio_292>311 so you prepare like all the changes to thank you 31 that are needed to to release and then you basically merge that those changes into the 311 Branch so you can see it in the python repo so sometimes what what happens is that you</transcript><transcript><audio_293>tag the comit before the merge um and uh and that's how it's supposed to be but like sometimes I made the mistake of tagging it after the merch and that triggers like a tacking a different comment because the merch commit is different and when you push it to GitHub then uh like 311 is not what you said</transcript> apparently the python was so so many jobs on the GI back and that it just just broke the whole website um that is not a mistake but like you know said it's a weird thing to say uh in in terms of actual mistakes I have made um hopefully like the the the good thing about mistakes as release managers that you can correct them and nobody sees them but some of the classic mistakes that I have made for instance that uh when when you finish like the release of a branch so let's say you're releasing 311 so you prepare like all the changes to thank you 31 that are needed to to release and then you basically merge that those changes into the 311 Branch so you can see it in the python repo so sometimes what what happens is that you tag the comit before the merge um and uh and that's how it's supposed to be but like sometimes I made the mistake of tagging it after the merch and that triggers like a tacking a different comment because the merch commit is different and when you push it to GitHub then uh like 311 is not what you said
{"source": "grass-yt-cc-by.0C4eKA5DXFs|shard_10016_22|create_multimodal_data.extract_yt_and_generate_transcripts.62|shard_10016|create_multimodal_data.generate_captions.42|shard_10016|create_multimodal_data.generate_captions.55", "params": {"id": "0C4eKA5DXFs", "channel_id": "UCHLnNgRnfGYDzPCCH8qGbQw", "duration": 4151, "view_count": 107, "age_limit": 0, "like_count": 3, "channel_follower_count": 6170, "license": "Creative Commons Attribution license (reuse allowed)", "uploader_id": "@PyConTaiwanVideo", "yt_tar_file": "/leonardo_work/EUHPC_E03_068/audio/fixed_download/grass-yt-cc-by//shard_10016/0C4eKA5DXFs.tar.gz"}}