Bug report

Expected Behavior - What were you expecting to happen?

On refresh, the application should be closed if the state of the same is wrongly configured or not following the HOCON format.

Current Behavior - What happens?

Nothing is communicated to the user nor the application crashes.

Possible Solution

Create a handler for exceptions that should close the application for critical/fatal exceptions.

What are the steps to reproduce this issue? (for bugs)

1. Start GEM with correct configuration
2. Remove and/or rename a repository ID without changing branches for an environment
3. Refresh GEM -> application is still working without updated configuration
4. Close GEM and re-start -> application does not start due to wrong configuration

Context

This is important for the use-case of git-configuration that somehow gets corrupted. Users should be informed so the configuration managers should update as soon as possible.

Any logs, error output, etc?

The logs contain the exception and stacktrace, but nothing is shown to the user.

Your Environment

• Version used: > 0.3.0
• Operating System and version (desktop or mobile): Windows