Handle interrupts and panics to mitigate data loss

This commit introduces a deferred call to a state teardown function
This is needed to properly flush data to the backing documentbuffer
as well as to truncate its underlying store. In doing so we make
sure data loss from process termination is minimal to nil.

when ever a panic happens or a signal is thrown the call to Teardown() is made

Signed-off-by: Ava Affine <ava@sunnypup.io>

internal/state/state.go

@@ -48,6 +48,7 @@ const (
 
 var eventMutex sync.RWMutex
 var eventSubscriptionCache = [NumEventTypes][]chan Event{}
+var eventStorageFileName string
 var eventStream docbuf.DocumentBuffer
 var maxEventsInMemory int
 
@@ -65,10 +66,29 @@ func Init(eventMemCacheSize int, eventStoreFileName string) error {
 		return errors.Join(errors.New(BadEventStreamInit), err)
 	}
 
+	eventStorageFileName = eventStoreFileName
 	maxEventsInMemory = eventMemCacheSize
 	return nil
 }
 
+// return no error. we are handling SIGINT
+func Teardown() {
+	// riskily ignore all locking....
+	// we are handling a termination signal after all
+	i, e := eventStream.Close()
+	if e != nil {
+		logging.Warn("failed to close document buffer: %s", e.Error())
+		logging.Warn("will attempt to truncate event store anyways")
+	}
+
+	e = os.Truncate(eventStorageFileName, i)
+	if e != nil {
+		logging.Error("FAILED TO TRUNCATE EVENT STORE!!")
+		logging.Error("You will likely have garbage data at the end of it")
+		logging.Error("Attempt manual correction!")
+	}
+}
+
 type EventType int8
 
 const (