Valentin Rothberg 142db01942 events endpoint: fix panic and race condition ... Fix a potential panic in the events endpoint when parsing the filters parameter. Values of the filters map might be empty, so we need to account for that instead of uncondtitionally accessing the first item. Also apply a similar for race conditions as done in commit f4a2d25c0f: Fix a race that could cause read errors to be masked. Masking such errors is likely to report red herrings since users don't see that reading failed for some reasons but that a given event could not be found. Another race was the handler closing event channel, which could lead to two kinds of panics: double close, send to close channel. The backend takes care of that. However, make sure that the backend stops working in case the context has been cancelled. Fixes: #6899 Signed-off-by: Valentin Rothberg <rothberg@redhat.com>		2020-07-21 16:56:26 +02:00
..
handlers	events endpoint: fix panic and race condition	2020-07-21 16:56:26 +02:00
server	Ensure umask is set appropriately for 'system service'	2020-07-06 14:21:17 -04:00
types	podman rmi: refactor logic	2020-04-21 08:12:25 +02:00
Makefile	Rewire ListContainers for APIv2 libpod	2020-02-11 08:14:28 -06:00
tags.yaml	network compatibility endpoints for API	2020-05-22 13:48:52 -05:00