From 990f57b2ef241c61aeb4b8f915ccd4b4bd048822 Mon Sep 17 00:00:00 2001
From: Martin Pitt <mpitt@redhat.com>
Date: Wed, 11 Oct 2023 18:17:46 +0200
Subject: [PATCH] React to health_status events

We previously didn't react to `health_status` events as they were
broken, and only reacted to `exec_died` instead. With the upcoming
podman release, `health_status` events are reliable, and they will also
not be accompanied by an `exec_died` event any more. So start updating
the container status on them.

Still keep listening to `exec_died` to support older podman releases.

Fixes #1443
---
 src/app.jsx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/app.jsx b/src/app.jsx
index 3118224b2..1910e7083 100644
--- a/src/app.jsx
+++ b/src/app.jsx
@@ -335,7 +335,6 @@ class Application extends React.Component {
         case 'export':
         case 'import':
         case 'init':
-        case 'health_status': // HACK: broken, https://github.com/containers/podman/issues/19237; see exec_died
         case 'kill':
         case 'mount':
         case 'prune':
@@ -360,7 +359,8 @@ class Application extends React.Component {
         case 'cleanup':
         case 'create':
         case 'died':
-        case 'exec_died': // HACK: pick up health check runs, see https://github.com/containers/podman/issues/19237
+        case 'exec_died': // HACK: pick up health check runs with older podman versions, see https://github.com/containers/podman/issues/19237
+        case 'health_status':
         case 'pause':
         case 'restore':
         case 'stop':