-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Fix Simple Auth Manager UI dev server not starting in breeze #60932
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@pierrejeambrun, it seems I'm not alone in this issue. Similar to the reverted fix: #60786 |
potiuk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice. TIl about pause()
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this problem is specific to --use-mprocs.
I tried both on main and can't reproduce, but if this fixes it for your setup go for it.
I tried this PR locally and both are working for me.
|
@pierrejeambrun Thanks for checking! Screen.Recording.2026-01-24.at.2.29.32.PM.movRegarding the point @potiuk mentioned about “Compile UI assets in dev mode” being overridden in the terminal, this appears to be related to a prek version upgrade. Screen.Recording.2026-01-24.at.2.48.39.PM.mov
|
|
@ephraimbuddy would you mind checking this as well when you have time? |
…eze (apache#60932) * Fix Simple Auth Manager UI dev server not starting in breeze * Redirected prek output to file in dev mode (cherry picked from commit ac765a6) Co-authored-by: Yeonguk Choo <choo121600@gmail.com>
…60932) * Fix Simple Auth Manager UI dev server not starting in breeze * Redirected prek output to file in dev mode


Problem
Second Vite dev server (Simple Auth Manager UI) never starts in breeze dev mode

Change
subprocess.run-->subprocess.Popenfor the first pnpm devsignal.pause()to keep the script alive so child processes stay in the same process groupScreen.Recording.2026-01-22.at.6.13.08.PM.mov
closes: #60930
Was generative AI tooling used to co-author this PR?
Generated-by: [claude] following the guidelines
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.