YoannAbriel opened a new pull request, #63259:
URL: https://github.com/apache/airflow/pull/63259
## Problem
Accessing the backfills API (`GET /ui/backfills`) returns a 500 error with
`PydanticSerializationError` when a backfill row has `dag_run_conf` set to
`None` in the database.
## Root Cause
`BackfillResponse.dag_run_conf` is typed as `dict`, which rejects `None`
during Pydantic serialization. Although the DB column is defined with
`nullable=False, default={}`, existing rows or edge cases can still have a
`None` value.
## Fix
Changed the type annotation from `dict` to `dict | None` in
`BackfillResponse` and the corresponding generated client model. Added a test
that creates a backfill with `dag_run_conf=None` and verifies the API returns
200.
Closes: #63257
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes — Claude Code
Generated-by: Claude Code following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information. Note: commit author/co-author name and email in commits
become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
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]
