Valentin Rothberg d856e87f40 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-20 11:37:05 +02:00
..
containers	Correctly print STDOUT on non-terminal remote exec	2020-07-10 17:15:33 -04:00
generate	move go module to v2	2020-07-06 15:50:12 +02:00
images	move go module to v2	2020-07-06 15:50:12 +02:00
manifests	move go module to v2	2020-07-06 15:50:12 +02:00
network	move go module to v2	2020-07-06 15:50:12 +02:00
play	move go module to v2	2020-07-06 15:50:12 +02:00
pods	move go module to v2	2020-07-06 15:50:12 +02:00
system	move go module to v2	2020-07-06 15:50:12 +02:00
test	events endpoint: fix panic and race condition	2020-07-20 11:37:05 +02:00
volumes	move go module to v2	2020-07-06 15:50:12 +02:00
bindings.go	V2 podman system connection	2020-06-23 08:18:53 -07:00
connection.go	move go module to v2	2020-07-06 15:50:12 +02:00
errors.go	move go module to v2	2020-07-06 15:50:12 +02:00