github-actions[bot] opened a new pull request, #75139:
URL: https://github.com/apache/airflow/pull/75139
Every run of the React UI unit tests printed about 13,000 lines of
"AggregateError: connect ECONNREFUSED ::1:3000 / 127.0.0.1:3000". The
shared msw server bypassed unhandled requests to localhost:3000, where
nothing listens, so the noise buried real failures and some tests
quietly exercised the "request failed" path instead of the one they
meant to.
The requests came from three places:
- Endpoints with no handler: the page shell (auth/me, auth/menus,
version, plugins, import errors, Dag warnings), the i18n bundles,
generic Dag, Dag run, task and task instance lookups, the grid and
graph structure, the Admin/Browse list pages, Dag list state counts
and teams, and the asset state store entry.
- Test files that started a second msw server next to the one in
testsSetup.ts. Two servers share msw's interception, so the global
one shadowed the file's handlers and closing either released
requests to the network.
- Requests sent while modules were still being imported (src/i18n/config
asks for the version and languages at module scope), before the
server started listening in beforeAll.
Add realistic default handlers, export one shared server that tests
extend with server.use(), start it at import time, and leave it open
since each test file runs in its own worker. Unhandled requests now
use the "error" strategy and fail the test that sent them. Two tests
needed adjusting: NotePreview no longer follows an external link to
airflow.apache.org, and Callbacks looks its button up again after the
translation bundles re-render the rows. The DagBreadcrumb loading-state
test now holds the run request pending explicitly instead of relying
on it failing.
(cherry picked from commit 941316b4640a58c1b71858218080a6c936375353)
Co-authored-by: Jarek Potiuk <[email protected]>
Generated-by: Claude Opus 5
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
