George Kiagiadakis 4ab119778a policy-node: when node.target is specified, wait a bit for the target to be available ... There is a chance of race condition here in case the client knows which target it wants to link to, but wireplumber has not yet "seen" this target because it is getting prepared asynchronously This may stall for up to 2 seconds clients that start streams with an invalid node.target property, but then they will be re-routed to the default node		2021-10-15 15:10:41 +03:00
..
access	access-portal: fix granting access to camera device nodes	2021-06-25 11:47:13 +03:00
monitors	scripts: add libcamera monitor	2021-10-06 10:22:36 +02:00
create-item.lua	policy: refactor/improve policy-node & session items to fix linking to monitors	2021-10-08 00:26:41 +03:00
default-routes.lua	default-routes: switch to the route when availability changed	2021-10-12 11:41:51 -04:00
intended-roles.lua	scripts: Add an intended-roles policy script	2021-06-20 18:45:28 -04:00
policy-endpoint-client-links.lua	s/metadatas/metadata/g	2021-06-18 10:44:24 +03:00
policy-endpoint-client.lua	policy-endpoint-client: decrease log message verbosity	2021-10-08 00:26:41 +03:00
policy-endpoint-device.lua	policy: refactor/improve policy-node & session items to fix linking to monitors	2021-10-08 00:26:41 +03:00
policy-node.lua	policy-node: when node.target is specified, wait a bit for the target to be available	2021-10-15 15:10:41 +03:00
restore-stream.lua	restore-stream.lua: do not remove target.node manually	2021-10-15 14:37:49 +03:00
static-endpoints.lua	static-endpoints: avoid capturing session item reference in the activate closure	2021-04-12 16:04:34 +03:00
suspend-node.lua	suspend-node: honor "session.suspend-timeout-seconds"	2021-02-18 09:15:24 +02:00