Sanitize error message in DatabricksExecutionTrigger

[fabbuc-gyg]

What

Strip characters that Postgres jsonb cannot store (NUL bytes and unpaired UTF-16 surrogates) from a failed Databricks task's error text, in both extract_failed_task_errors and extract_failed_task_errors_async.

Why

DatabricksExecutionTrigger puts each failed task's error into its TriggerEvent which gets persisted in the deferred task instance's next_kwargs, which is a Postgres jsonb column. Since Databricks output can contain NUL bytes, postgres rejects this with an error like this:

sqlalchemy.exc.DataError: (psycopg2.errors.UntranslatableCharacter) unsupported Unicode escape sequence
DETAIL: \u0000 cannot be converted to text.

Because the invalid event is retried, the triggerer enters a CrashLoopBackOff which makes it unhealthy.

How

A small make_jsonb_safe() helper regex-strips \x00 and \ud800-\udfff from the error string (non-string values pass through unchanged). It is applied to the extracted error in both the sync and async helpers, so the emitted trigger event is always persistable.

Tests

Added unit tests in providers/databricks/tests/unit/databricks/utils/test_databricks.py:

• direct make_jsonb_safe cases (NUL strip, unpaired-surrogate strip, clean-text passthrough, non-string passthrough)
• extract_failed_task_errors and extract_failed_task_errors_async sanitize error output

---

Was generative AI tooling used to co-author this PR?

• Yes - Cursor was used to help draft this change; the author reviewed it.

Generated-by: Cursor

Made with Cursor

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example Dag that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[eladkal]

cc @moomindani for Databricks team review