Zain Rizvi

Thanks! This is a really useful bit of functionality. I bet a lot of people would love it being integrated into the main 'applause-button' library :)

This also reproduces if you try to extract audio from a CompositeVideoClip: `CompositeVideoClip([...]).audio.write_audiofile("my-audio.mp3") ` Which results in the error: ``` --------------------------------------------------------------------------- AttributeError Traceback (most recent call last) in ----> 1...

@pytorchmergebot merge -l The failing test is flaky ([proof](https://hud.pytorch.org/failure/test_vmap_exhaustive_linalg_ldl_solve_cuda_float32)). [Filed a ticket](https://github.com/pytorch/pytorch/issues/85341) to alert the owning team and disable this test from blocking any more builds

Safari on mobile reproduces this for me as well

Do legitimate flaky failures tend to have generic error captures like `##[error]Process completed with exit code 1.`? Using a generic output like that to determine flakiness seems really risky, even...

@pytorchbot merge -r Just a person to push the merge button :) Fyi, the above text is the magic incantation to do it

@pytorchbot merge

The one-line change didn't work for me. Instead, I had to write a custom script to generate the YouTube handle, and then I could pass that handle in to the...

Also, adding the `ciflow/inductor` label to your PR will help trigger extra inductor tests which normally don't get run on PRs but do get run once they're merged into master...

If we have specific files/folders that should always trigger periodic builds, we could use auto-labeler to tag those PRs with the periodic label and kick off those builds https://github.com/pytorch/pytorch/blob/master/.github/labeler.yml