fix: bad timestamp values could crash log command

src/commands/logs.ts

@@ -48,7 +48,19 @@ export class LogsCommand extends Command<typeof logsArgs, typeof logsOpts> {
     // TODO: use basic logger (no need for fancy stuff here, just causes flickering)
     stream.forEach((entry) => {
       // TODO: color each service differently for easier visual parsing
-      ctx.log.info({ section: entry.serviceName, msg: [entry.timestamp.toISOString(), chalk.white(entry.msg)] })
+      let timestamp = "                        "
+
+      // bad timestamp values can cause crash if not caught
+      if (entry.timestamp) {
+        try {
+          timestamp = entry.timestamp.toISOString()
+        } catch { }
+      }
+
+      ctx.log.info({
+        section: entry.serviceName,
+        msg: [timestamp, chalk.white(entry.msg)],
+      })
     })
 
     // NOTE: This will work differently when we have Elasticsearch set up for logging, but is

src/plugins/kubernetes/actions.ts

@@ -344,6 +344,7 @@ export async function getServiceLogs(
 
   const namespace = await getAppNamespace(ctx, provider)
   const proc = kubectl(context, namespace).spawn(kubectlArgs)
+  let timestamp: Date
 
   proc.stdout
     .pipe(split())
@@ -352,7 +353,9 @@ export async function getServiceLogs(
         return
       }
       const [timestampStr, msg] = splitFirst(s, " ")
-      const timestamp = moment(timestampStr).toDate()
+      try {
+        timestamp = moment(timestampStr).toDate()
+      } catch { }
       stream.write({ serviceName: service.name, timestamp, msg })
     })