Skip to content

fix(bb-app): bound startup restart failures - #3339

Open
MPIsaac-Per wants to merge 1 commit into
get-bb:mainfrom
MPIsaac-Per:bb/mpi-1663-startup-failure-backoff-thr_5ctv48gfau
Open

fix(bb-app): bound startup restart failures#3339
MPIsaac-Per wants to merge 1 commit into
get-bb:mainfrom
MPIsaac-Per:bb/mpi-1663-startup-failure-backoff-thr_5ctv48gfau

Conversation

@MPIsaac-Per

@MPIsaac-Per MPIsaac-Per commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Human comments

What was wrong

The full-stack launcher retried failed child starts at a fixed interval without a terminal state. Diagnostic artifacts were unbounded and could remain empty when their filesystem writes failed. Startup storage errors before child supervision could also escape as a generic exit.

What changed

  • Exponential, abortable restart backoff with an eight-failure terminal exit (75).
  • Stable-lifecycle accounting based on the child exit time.
  • Terminal stderr reporting for storage failures during startup, runtime-file setup, and cleanup.
  • Atomic diagnostic artifacts, cleanup on failed rename, and a five-per-process-and-kind retention cap.

How you verified

pnpm exec turbo run test typecheck --filter=bb-app --filter=@bb/process-utils

  • bb-app: 83 tests passed.
  • @bb/process-utils: 22 tests passed.

Fixes #3340

AGENT GENERATED

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bb-app startup failures retry indefinitely and accumulate empty diagnostic files on disk failure

1 participant