* Update tinydb manager test to current api
* Add tinydb parallel tests to CI
* Use filelock library to help make tinydb threadsafe
The tests for parallel access sometimes failed with the previous
implementation. I'm currently not 100% sure why, but it might have
to do with the fact that the file is already created in the TinyDB
constructor which was not protected by a lock.
Also not protecting the reads can read to invalid reads in the case
when a read and a write happen simultaneously and the read catches
partially written data.
This implementation allows for fewer concurrency but is quite simple,
so we should be able to be confident about its safety.
Also the TinyDB manager is not intended for high performance and its
IO operations are orders of magnitude faster than requests over the
network or process executions anyway.
totycro
f6a055e8e1