{"push_id":1567912251,"size":1,"distinct_size":1,"ref":"refs/heads/add-sensorlock","head":"ad953519970a34c3be68806ac728587ba2711e44","before":"89bde94d28f9bdbb2c1d12e44881580cd2d779d0","commits":[{"sha":"ad953519970a34c3be68806ac728587ba2711e44","author":{"name":"albert","email":"981b46b6fc9d7ffc66cbb707de6b409889a93df7@univie.ac.at"},"message":"Add a \"sensor lock\" to mutex sensor access (WIP)\n\nThis is in response to aaaaalbert/sensibility-testbed#19, \"Stopping\none sensor-reading sandbox crashes all native parts\".\n\nUsing the sensor lock, we ensure that `harshexit` does not send\ntermination signals to the sandbox while a sensor call is in progress.\n* The new `repysensors` module implements a generic wrapper that uses\n  the sensor lock;\n* We wrap the `sensors.get_acceleration` call in `namespace.py`;\n* `harshexit` blocks until any pending sensor calls have returned,\n  and only then issues an `os.kill`.\n\nNow, two vessels that both access the accelerometer can be started\nand stopped independent from each other and the rest of the app.\n\nIf the fix turns out to work sufficiently fast, I'll go and wrap\nthe other sensor calls likewise.","distinct":true,"url":"https://api.github.com/repos/SensibilityTestbed/repy_v2/commits/ad953519970a34c3be68806ac728587ba2711e44"}]}
{"actor":{"display_login":"aaaaalbert"}}