1.2.35

Fix receiving sigkill after pulling job from stack but before starting forking

Before if we received a sigkill after pulling from stack but before starting the forking process, we would end up handling the sigkill, then resuming the forking process. The child process would be started, and then hard killed once the parent process was done shutting itself down, resulting in a stranded job.