From 0e02998fafaa5794afcdd75de8ab07b307e35b1c Mon Sep 17 00:00:00 2001
From: Jonas Hermsmeier <jhermsmeier@gmail.com>
Date: Fri, 17 Nov 2017 14:36:21 +0100
Subject: [PATCH] fix(gui): Re-enable printing progress in console (#1853)

Change-Type: patch
---
 lib/gui/app.js | 17 ++++++-----------
 1 file changed, 6 insertions(+), 11 deletions(-)

diff --git a/lib/gui/app.js b/lib/gui/app.js
index e3f2ce35..6dc8ba9a 100644
--- a/lib/gui/app.js
+++ b/lib/gui/app.js
@@ -185,20 +185,15 @@ app.run(() => {
 
     const currentFlashState = flashState.getFlashState()
 
-    // There is usually a short time period between the `isFlashing()`
+    // NOTE: There is usually a short time period between the `isFlashing()`
     // property being set, and the flashing actually starting, which
     // might cause some non-sense flashing state logs including
     // `undefined` values.
-    //
-    // We use the presence of `.eta` to determine that the actual
-    // writing started.
-    if (!currentFlashState.eta) {
-      analytics.logDebug(
-        `Progress (${currentFlashState.type}): ` +
-        `${currentFlashState.percentage}% at ${currentFlashState.speed} MB/s ` +
-        `(eta ${currentFlashState.eta}s)`
-      )
-    }
+    analytics.logDebug(
+      `Progress (${currentFlashState.type}): ` +
+      `${currentFlashState.percentage}% at ${currentFlashState.speed} MB/s ` +
+      `(eta ${currentFlashState.eta}s)`
+    )
 
     windowProgress.set(currentFlashState)
   })