You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
reflex deploy hides its progress and success messages: the export step leaves the console at WARNING #7850
reflex deploy exports the app first (reflex/hosting.pyexport_for_deploy -> reflex/utils/export.pyexport(loglevel=config.loglevel.subprocess_level())). export() calls console.set_log_level(loglevel) with the subprocess level, which for the default INFO level is WARNING, and never restores the previous level. Everything the hosting CLI logs at INFO after the export is therefore hidden: the deployment progress, the scaling-conflict retry messages added in 0.10.1 (#7463, retries can take up to ~165 s), and the final success line. A non-TTY deploy (CI) is silent from the upload bar until the process exits; warnings and errors are still shown.
--loglevel info does not help either: set_log_level only writes REFLEX_LOGLEVEL when the level changes, so the explicit flag never reaches the config. Workaround: REFLEX_LOGLEVEL=info reflex deploy ....
Not a regression (the mechanism dates back to 0.8); the newer progress messages make it more visible. Last verified on 0.10.1a1 with reflex-hosting-cli 0.2.1a1; the code path is unchanged on main.
Repro
reflex deploy (or reflex deploy --loglevel info) from a non-TTY shell, e.g. reflex deploy ... | cat. After the export, no INFO lines appear until exit; with --loglevel debug they do.
Expected vs actual
Expected: after the export step, the console is back at the level the user asked for (default INFO), so progress and the success line are shown.
Actual: console stays at WARNING for the rest of the command.
Fix direction
Code: export() in reflex/utils/export.py (the console.set_log_level(loglevel) call) and export_for_deploy() in reflex/hosting.py.
Restore the previous console level when export() returns (try/finally), or have export() pass the subprocess level only to the subprocesses it starts instead of changing the parent's console level.
Check how --loglevel reaches REFLEX_LOGLEVEL in the CLI so an explicit --loglevel info is honoured even when it equals the current level.
Non-goals: no change to the subprocess output level (the noisy build output should stay hidden by default).
Tests: a unit test that export() leaves the console level unchanged, and one for --loglevel info being honoured.
Activity
linear-code commentedon Nov 11, 2026
ENG-13998
zeyadrabie commentedon Nov 21, 2026
#7947 handles the export() side, so I opened #7960 for the --loglevel side without overlapping it.