reflex-dev/reflex - CodSpeed

reflex

Blog Docs Changelog

Performance History

Latest Results

Update news/+mixin-inherited-var-shadow.bugfix.md Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>

qubydev:fix/minix-silent-shadow

14 hours ago

fix: gate the node version check only at runtime, not during init

flcrom:fix/npm-preflight-before-install

14 hours ago

mixin vs mixin conflict resolved

qubydev:fix/minix-silent-shadow

14 hours ago

test: treat a mid-check reap as gone in the process-gone probe

flcrom:fix/notty-signal-shutdown

16 hours ago

fix: key the npm node-version gate on the selected package manager

flcrom:fix/npm-preflight-before-install

16 hours ago

fix: gate npm installs on the node version preflight

flcrom:fix/npm-preflight-before-install

17 hours ago

fix: terminate the frontend process tree when reflex run shuts down Without a TTY, SIGTERM/SIGINT stopped the Granian backend but left the frontend dev server running: run_concurrently_context then blocked forever waiting on the thread streaming the child's output, and only SIGKILL of the whole process group stopped the launcher. Children spawned by run tasks are now tracked in a context-scoped registry (thread-local binding, so unrelated new_process callers are never touched) and terminated when the context unwinds - on normal exit, KeyboardInterrupt, and body failure alike. The frontend dev server runs in its own session on POSIX, so teardown signals its whole process group and grandchildren cannot survive holding the output pipe open. On Windows the tree is terminated via psutil. Late registrations during shutdown are terminated immediately. Closes #6980

flcrom:fix/notty-signal-shutdown

17 hours ago

fix: terminate the frontend process tree when reflex run shuts down Without a TTY, SIGTERM/SIGINT stopped the Granian backend but left the frontend dev server running: run_concurrently_context then blocked forever waiting on the thread streaming the child's output, and only SIGKILL of the whole process group stopped the launcher. Children spawned by run tasks are now tracked in a context-scoped registry (thread-local binding, so unrelated new_process callers are never touched) and terminated when the context unwinds - on normal exit, KeyboardInterrupt, and body failure alike. The frontend dev server runs in its own session on POSIX, so teardown signals its whole process group and grandchildren cannot survive holding the output pipe open. On Windows the tree is terminated via psutil. Late registrations during shutdown are terminated immediately. Closes #6980

flcrom:fix/notty-signal-shutdown

18 hours ago

Latest Branches

0%

Reject inherited state var shadowing through mixins#7206

14 hours ago

467752c

qubydev:fix/minix-silent-shadow

0%

fix: gate npm installs on the node version preflight#7210

15 hours ago

f27cab1

flcrom:fix/npm-preflight-before-install

0%

Terminate the frontend process tree when reflex run shuts down#7209

16 hours ago

1dc88f2

flcrom:fix/notty-signal-shutdown

© 2026 CodSpeed Technology

Home Terms Privacy Docs