Limit logs and write logs to file that can be opened by user

[dpgraham]

• Limit logs to 1000
  • When logs get above 1000, the app slows down/crashes. Limit the number of rendered logs to 1000
• Log writing
  • Main thread writes all logs to file
  • Main thread sends the filepath of the logs to the browser window
  • Added 'GetRawLogsButton' to server monitor component
  • When button is clicked, opens the file externally
  • Delete logfile when browser closed
  • If logfile not present, show an alert to indicate that logs can't be accessed

[jlipps]

made a few comments. also i've scanned this a few times and i don't see where you're actually chopping off the log entries in the browser

[jlipps]

don't need quotes around flag

[jlipps]

this would look better on multiple lines. one line for the map, the other for the write.

[jlipps]

could we share some of this code with .stopButton?

[dpgraham]

Fixed the branch so that you can see the slicing in this commit: f0c997d

[dpgraham]

Fixes pushed

[jlipps]

this is no longer a TODO, right?

[jlipps]

let

[dpgraham]

That's an eslint rule. Apparently you can't declare using let inside of switch statements.

I'll just move the declaration outside of it instead.

[imurchie]

Yeah, case statements aren't blocks, so the variables are hoisted to the top of the switch statement, but uninitialized until the case it executed. This isn't so good.

The best solution would be to wrap the case stuff into a block.

case LOGS_RECEIVED: {
  // TODO: We should dump logs to a txt file that can be exported
  let logLines = state.logLines.concat(action.logs.map((l) => {
    // attach a timestamp to each log line here when it comes in
    l.timestamp = moment().format('YYYY-MM-DD hh:mm:ss');
    return l;
  }));

  // Don't log more than MAX_LOG_LINES
  if (logLines.length > MAX_LOG_LINES) {
    logLines = logLines.slice(logLines.length - MAX_LOG_LINES);
  }

  return {
    ...state,
    logLines,
    serverStatus: STATUS_RUNNING
  };
}