Sync v3-2-stable with v3-2-test to release 3.2.2rc3#67566
Merged
Conversation
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…path (#67548) (#67556) * UI: Fix Monaco workers crashing in production mode `?url` does not run the Vite worker pipeline. For `editor.worker.js` it inlines the raw source as a base64 data URL (the source is below the default `assetsInlineLimit`), and the inlined module still has bare specifier imports it cannot resolve in a Worker context. For `json.worker.js` it copies a partly-bundled file whose top-level `import '../../editor/editor.worker.js'` resolves to a path that does not exist in the build output. Both cases manifest at runtime as "Could not create web worker(s). Falling back to loading web worker code in main thread" followed by a stream of fallback fetch errors. Switch to `?worker&url`: Vite runs the file through the worker pipeline (bundling all dependencies into a self-contained IIFE) and the URL query suffix returns the resulting URL as a string instead of a Worker constructor. The Blob shim from #67352 then imports a properly bundled worker, restoring real worker-thread execution. * UI: Rewrite modulepreload hrefs to the api-server static path Vite emits both `<script src="./assets/...">` and `<link rel="modulepreload" href="./assets/...">` for chunks in the built `index.html`. The `transform-url-src` plugin only rewrote `src="./assets/"` to `src="./static/assets/"`, leaving the modulepreload `href`s untouched. Behind the api-server's `/static/` mount those preload requests hit the SPA HTML fallback and the browser fails them with `Expected a JavaScript-or-Wasm module script but the server responded with a MIME type of "text/html"`. The chunks themselves still load via `<script src>` so the app works, but every page load wastes three round-trips on the failed preloads and floods the console. Apply the same `static/` rewrite to `href="./assets/"` and switch all three rewrites to `replaceAll` so multiple matches (one per chunk) are handled — `replace` with a string only touches the first occurrence. --------- (cherry picked from commit eff567c) Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com> Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com>
vatsrahul1001
requested review from
XD-DENG,
amoghrajesh,
ashb,
bbovenzi,
bugraoz93,
choo121600,
dheerajturaga,
ephraimbuddy,
gopidesupavan,
guan404ming,
hussein-awala,
jason810496,
jedcunningham,
jscheffl,
kaxil,
pierrejeambrun,
potiuk,
ryanahamilton,
shubhamraj-git and
vincbeck
as code owners
boring-cyborg
Bot
added
area:airflow-ctl
area:API
boring-cyborg
Bot
added
area:logging
area:production-image
potiuk
approved these changes
May 26, 2026
jscheffl
approved these changes
May 26, 2026
amoghrajesh
approved these changes
May 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Time for 3.2.2rc3
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.