Better error handling, less .unwraps()

Some of these unwraps are fine to stay, mostly those that deal with
locks - in this case, crashing the program if something goes wrong is
probably fine.

However, we also had a lot of other places where we panic'd on errors,
even though we really shouldn't have. For example, an invalid zip file
would bring down the whole scanner. In this case, we now use proper
Result<>s and we log the error.

Some places stay with unwrap() for now, mainly the code that is rare and
obvious when it goes wrong - such as an overflow in input values. It
could be made nicer, but it is not a priority for now.

Some unwraps() have been changed to expect() to signal why they
shouldn't fail.

1 files changed, 6 insertions, 4 deletions

diff --git a/src/output/pipeline.rs b/src/output/pipeline.rs
index 9b7f461..3db0d56 100644
--- a/src/output/pipeline.rs
+++ b/src/output/pipeline.rs
@@ -3,6 +3,8 @@ use super::{aggregators::Aggregator, formats::Format};
 
 use std::{io::Write, sync::Mutex};
 
+use anyhow::Result;
+
 pub struct Pipeline {
     format: Box<dyn Format>,
     aggregator: Box<dyn Aggregator>,
@@ -22,13 +24,13 @@ impl Pipeline {
         }
     }
 
-    pub fn push_item(&self, item: LogResult) {
+    pub fn push_item(&self, item: LogResult) -> Result<()> {
         let mut writer = self.writer.lock().unwrap();
-        self.aggregator.push_item(item, &*self.format, &mut *writer);
+        self.aggregator.push_item(item, &*self.format, &mut *writer)
     }
 
-    pub fn finish(self) {
+    pub fn finish(self) -> Result<()> {
         let mut writer = self.writer.lock().unwrap();
-        self.aggregator.finish(&*self.format, &mut *writer);
+        self.aggregator.finish(&*self.format, &mut *writer)
     }
 }