Version 0.1.2
-
The server uses a pool of child processes to run diffs. If the pool breaks while running a diff, it will be re-created once, and, if it fails again, the server will now crash with an exit code of
10. (An external process manager like Supervisor, Kubernetes, etc. can then decide how to handle the situation.) Previously, the diff would fail at this point, but server would try to re-create the process pool again the next time a diff was requested. You can opt-in to the old behavior by setting theRESTART_BROKEN_DIFFERenvironment variable totrue. (#49) -
The diff server now requires Sentry 1.x for error tracking.