Add missing reference to err in catch block

[austinandrews]

Overview master is marked as the default branch so making a PR to that branch, but would probably be better to protect it and do periodic releases from the develop or development branch.

Anyways, was giving the new app a spin (cool stuff) and was having trouble getting the process logs to load. Looked at the console and err was undefined on line 308 of commands.tsx. So I fixed that and now the process logs seem to be working.

Testing If I recall correctly this repo has a Travis check that runs tests so we will see (Jest failed when I tried to run them locally against a locally running version of the app).

Further discussion I'm not sure who the most recent maintainers are, I just tagged the reviewer that GH suggested to me. Feel encouraged to weigh in even if you haven't been tagged.

[d-hp]

Hey Austin,

Thank you for checking out our application and reaching out. We appreciate it!

Git/GitHub Workflow

• I will follow-up tomorrow in regards to protecting the master branch as I would like to ensure that this configuration was not done intentionally. I agree that all PRs should be made to the develop branch to ensure functionality.

Process Logs

• The current issue with Process Logs has to do with selecting multiple running containers prior to clicking the Get Logs button. Were you having issues getting any process logs rendered even with a single selection?

Testing Check & CI/CD

• We removed the CI/CD and unfortunately were not able to ensure that existing testing suites were fully functional/compatible with the new source code.
• We felt that significant refactoring of the client-side source code would be advantageous to future contributors. In addition, server-side code was added to an application that was intended to be utilizing Electron which ultimately made it challenging/unconventional to build the Electron binaries required to package our application for distribution. With this in mind, we made the decision to reevaluate the high-level design of Docketeer in hope that this can be a legitimate utility to developers prioritizing ease of integration into existing workflows.
• Although we truly do wish we had the time to re-implement testing suites & re-configure the CI pipeline, we felt that it was important to prioritize the aforementioned issues.

Thank you so much for your contribution and advice on our release. Please resubmit the PR to the develop branch when time permits and I will happily approve it.