[harsh21234i]

Summary

• Bound shutdown after the first interrupt, including while output is being drained.
• Isolate the POSIX child process group so Ctrl-C is forwarded exactly once.
• Keep shutdown handlers active through drain and ignore repeated signals.
• Bound oversized JSON records to the pipe's atomic-write limit so every emitted line remains parseable.
• Add regression coverage for repeated Ctrl-C/SIGTERM, oversized records, drain cleanup, and forced test-process cleanup.
• Add the Reflex Base bugfix news fragment.

Tests

• tests/units/reflex_base/utils/test_log.py: 81 passed, 5 skipped on Windows (POSIX-only cases).
• Linux Docker smoke tests: group SIGINT forwarded once; oversized output stayed valid JSON; blocked drain remained bounded after a second SIGTERM.
• Ruff formatting, focused lint, and git diff --check passed.

Fixes #7510

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The changes since the previous review appear safe to merge.

Summary

This PR adds a shutdown deadline for JSON output and shortens oversized records written during shutdown.

• Child output shutdown keeps one deadline active through the drain.
• Pipe output keeps complete records and shortens oversized shutdown lines.

_{Reviews (9) · Last reviewed commit: "fix(logging): preserve records in interr..." · Reviewed by Greptile}

[codspeed]

Merging this PR will not alter performance

1 warning

⚠️ 20 benchmarks are dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

✅ 148 untouched benchmarks

---

_{Comparing harsh21234i:fix/7510-bounded-json-drain (f3f4a20) with main (a9b6613)}

[cubic-dev-ai]

All reported issues were addressed across 3 files

<sub>Reply with feedback, questions, or to request a fix.

View guided diff | Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed

<sub>Reply with feedback, questions, or to request a fix.

View guided diff | Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 3 files (changes from recent commits).

<sub>Reply with feedback, questions, or to request a fix.

View guided diff | Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 2 files (changes from recent commits).

<sub>Reply with feedback, questions, or to request a fix.

View guided diff | Re-trigger cubic</sub>

[masenf]

Main now includes #7558, which deliberately keeps the child in the supervisor's process group so terminal Ctrl-Z and a process-group SIGKILL still reach the app (review rationale). This PR's start_new_session=True / os.killpg(proc.pid, ...) shutdown path conflicts with that decision in log.py.

A mechanical conflict resolution would either reintroduce the orphaned-child behavior or discard this PR's bounded shutdown behavior. The bounded drain needs to be reconciled with the shared-process-group behavior before a safe main merge. I have left the branch intact for that author/reviewer decision.