Peter Šurda
e5e9955cd9
- add a ffmpeg process to kivy tests if it detects running inside docker
- this approach can be reused for other tests that may benefit from a
video
- it may be possible to do this in bash, outside of python, but that
would exacerbate the process synchronisation issues, as outlined here:
- X server must be running before ffmpeg starts, otherwise ffmpeg
can't record and quits
- ffmpeg must end before the X server ends, as otherwise it segfaults
and video will be incomplete
- ffmpeg must start before the actual tests start and stop after the
tests stop, otherwise a part of the tests will be missing from the
recording
- this approach I chose here avoids most synchronisation issues.
If ffmpeg takes more than 2 seconds to start recording (unlikely), a
part of the video will be missing. Also if for some reason ffmpeg is
too slow, then also we may end up with a truncated video, at the end.
- I chose lossless vp9 codec with webm format, this appears to work on
firefox and chrome. Safari refuses to show the video even though it
should be supported.
|
||
|---|---|---|
| .buildbot | ||
| buildscripts | ||
| desktop | ||
| dev | ||
| docs | ||
| man | ||
| packages | ||
| src | ||
| .gitattributes | ||
| .gitignore | ||
| .readthedocs.yml | ||
| .travis.yml | ||
| checkdeps.py | ||
| COPYING | ||
| Dockerfile | ||
| INSTALL.md | ||
| kivy-requirements.txt | ||
| LICENSE | ||
| MANIFEST.in | ||
| PULL_REQUEST_TEMPLATE.md | ||
| pybitmessage | ||
| README.md | ||
| requirements.txt | ||
| run-kivy-tests-in-docker.sh | ||
| run-tests-in-docker.sh | ||
| setup.cfg | ||
| setup.py | ||
| start.sh | ||
| stdeb.cfg | ||
| tests-kivy.py | ||
| tests.py | ||
| tox.ini | ||
PyBitmessage
Bitmessage is a P2P communication protocol used to send encrypted messages to another person or to many subscribers. It is decentralized and trustless, meaning that you need-not inherently trust any entities like root certificate authorities. It uses strong authentication, which means that the sender of a message cannot be spoofed. BM aims to hide metadata from passive eavesdroppers like those ongoing warrantless wiretapping programs. Hence the sender and receiver of Bitmessages stay anonymous.
Development
Bitmessage is a collaborative project. You are welcome to submit pull requests although if you plan to put a non-trivial amount of work into coding new features, it is recommended that you first describe your ideas in the separate issue.
Feel welcome to join chan "bitmessage", BM-2cWy7cvHoq3f1rYMerRJp8PT653jjSuEdY