Christian Kellner e5b12e55f4 objectstore: transparant access for floating objs ... A "floating" object is a temporary object that is identified, i.e. has an `id` and is thus also locked, but is not committed to the store. The `contains` and `get` methods of ObjectStore will now return such floating objects as if they were committed ones, provind transparent access to object that have been built during the exectuin of osbuild.		2021-01-15 13:20:31 +01:00
..
formats	formats: describe now takes a manifest	2021-01-09 18:09:47 +01:00
util	util/jsoncomm: chain the BufferError in recv	2020-10-30 17:28:31 +01:00
__init__.py	osbuild: introduce Manifest class	2021-01-09 18:09:47 +01:00
__main__.py	osbuild: always return exit code	2020-10-27 22:04:09 +01:00
api.py	api: ensure parent of socket dir exists	2020-12-04 12:28:30 +01:00
buildroot.py	buildroot: continuously stream log data to monitor	2020-10-28 14:28:07 +01:00
loop.py	loop: use python 3 style base class initialization	2020-10-30 17:28:31 +01:00
main_cli.py	pipeline: run method takes store object not dir	2021-01-15 13:20:31 +01:00
meta.py	formats/v1: move validation logic here	2021-01-09 18:09:47 +01:00
monitor.py	monitor: add assembler/stage duration	2020-08-06 16:19:47 +02:00
objectstore.py	objectstore: transparant access for floating objs	2021-01-15 13:20:31 +01:00
pipeline.py	pipeline: don't use a non-existing base for trees	2021-01-15 13:20:31 +01:00
remoteloop.py	api: remove 'addr' param from message dispatcher	2020-07-29 02:16:20 +01:00
sources.py	api: remove 'addr' param from message dispatcher	2020-07-29 02:16:20 +01:00
treesum.py	treesum: don't use dir_fd parameter in os.scandir()	2019-11-29 00:45:14 +01:00