GitHub user hinchliff added a comment to the discussion: Unable to redact value 
of type SIGSEGV

the full exception log from `secrets_masker.py` -- 

```
[2025-02-20T19:44:42.794+0000] {secrets_masker.py:282} WARNING - Unable to 
redact value of type 
******************************************* Received SIGSEGV 
*******************************************
SIGSEGV (Segmentation Violation) signal indicates Segmentation Fault error 
which refers to
an attempt by a program/library to write or read outside its allocated memory.

In Python environment usually this signal refers to libraries which use low 
level C API.
Make sure that you use right libraries/Docker Images
for your architecture (Intel/ARM) and/or Operational System (Linux/macOS).

Suggested way to debug
======================
  - Set environment variable 'PYTHONFAULTHANDLER' to 'true'.
  - Start airflow services.
  - Restart failed airflow task.
  - Check 'scheduler' and 'worker' services logs for additional traceback
    which might contain information about module/library where actual error 
happen.

Known Issues
============

Note: Only Linux-based distros supported as "Production" execution environment 
for Airflow.

macOS
-----
 1. Due to limitations in Apple's libraries not every process might 'fork' safe.
    One of the general error is unable to query the macOS system configuration 
for network proxies.
    If your are not using a proxy you could disable it by set environment 
variable 'no_proxy' to '*'.
    See: https://github.com/python/cpython/issues/58037 and 
https://bugs.python.org/issue30385#msg293958
********************************************************************************************************,
 please report this via <https://github.com/apache/airflow/issues>. Error was: 
RecursionError: maximum recursion depth exceeded
```

GitHub link: 
https://github.com/apache/airflow/discussions/46982#discussioncomment-12282160

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to