| ... | ... | @@ -11,4 +11,26 @@ |
|
|
|
- Reason 2: I don't like the feeling of `frame.side_data.get('MOTION_VECTORS')`. Perhaps `frame.side_data.motion_vectors` is better, or just `frame.motion_vectors`. This speaks to how flags and such are exposed as well.
|
|
|
|
|
|
|
|
- Auto flushing/muxing of streams.
|
|
|
|
Perhaps `stream.encode_and_mux(frame)` is a new API that would take responsibility. We would have to assert that you don't blend the two of them. |
|
|
\ No newline at end of file |
|
|
|
Perhaps `stream.encode_and_mux(frame)` is a new API that would take responsibility. We would have to assert that you don't blend the two of them.
|
|
|
|
|
|
|
|
- Planes increase the buffer refcounts instead of holding onto frame reference (via `av_frame_get_plane_buffer`).
|
|
|
|
|
|
|
|
- Auto sdist and upload after a successful test when there is a tag
|
|
|
|
- TWINE_USERNAME and TWINE_PASSWORD secrets/envvars
|
|
|
|
|
|
|
|
- build caching?
|
|
|
|
- idea 1: rsync to my server
|
|
|
|
|
|
|
|
- idea 2: zip to my server via SSH
|
|
|
|
- How to stuff a SSH key into a secret: https://www.webfactory.de/blog/use-ssh-key-for-private-repositories-in-github-actions
|
|
|
|
- secrets: https://help.github.com/en/articles/virtual-environments-for-github-actions#creating-and-using-secrets-encrypted-variables
|
|
|
|
- make pyav user on one of my servers that can only do this stuff; can it be chrooted?
|
|
|
|
- try to download cache for the branch, and then develop
|
|
|
|
|
|
|
|
- ssh pyav.mikeboers.com 'cat > cache/$BRANCH/docs.zip' < docs.zip
|
|
|
|
- wget cache.pyav.mikeboers.com/$BRANCH.docs.zip
|
|
|
|
|
|
|
|
- should I have one which does the sdist, and then the rest compile that?
|
|
|
|
doesn't really seem like it would save much time TBH.
|
|
|
|
|
|
|
|
cached-build (--get|--put) [--etag FOO] name directory |
|
|
\ No newline at end of file |
