Eliminating Non-Deterministic Exit Codes in StayPresent

This is a submission for *DEV's Summer Bug Smash: Clear the Lineup** powered by Sentry.*

Project Overview

StayPresent is an open-source Python library for supervising long-running bots and background services. It automatically restarts crashed bots, monitors their health, and exits with an appropriate status code when recovery is no longer possible.

While reviewing the crash recovery logic, I discovered that identical failures could sometimes produce different process exit codes.

Eliminating Non-Deterministic Exit Codes in StayPresent

Related reading

# I Fixed a Shutdown Race Condition That Could Leave Bot Processes Running…

The smolagents bug that made my agent retry the same valid code three times

Sentry Bug Operations Demo

I Used Sentry to Expose a Silent Data-Loss Bug with Zero Errors

The Counter That Counted a Call the Preflight Never Reached

One Event-Loop Turn, One False Redis Capacity Error

Related reading

# I Fixed a Shutdown Race Condition That Could Leave Bot Processes Running…

The smolagents bug that made my agent retry the same valid code three times

Sentry Bug Operations Demo

I Used Sentry to Expose a Silent Data-Loss Bug with Zero Errors

The Counter That Counted a Call the Preflight Never Reached

One Event-Loop Turn, One False Redis Capacity Error