dgtlmoonandClaude Opus 5.5 94d3404d88 Notifications - |regex_replace ReDoS timeout now works in any thread (use 'regex' package timeout=) (#4585) ...

* Notifications - |regex_replace ReDoS timeout now works in any thread, use the 'regex' package timeout= instead of SIGALRM

signal.alarm() can only be set from the main thread, but notifications are rendered
in the notification runner threads and previews in the Flask request threads, so
since #4577 the timeout was effectively never applied in production.

Re #3501, follow-up to #4577

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* regex_replace - Allow the timeout to be set with the REGEX_TIMEOUT_SECONDS env var

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* regex_replace - Import 'regex' lazily inside the filter, saves ~2MB RSS per instance that never uses it

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-23 15:31:51 +02:00

..

__init__.py

feat(jinja2): add unixtime filter to format Unix timestamps in notifications (#3641) (#4503)

2026-10-07 16:24:24 +02:00

datetime_fmt.py

feat(jinja2): add unixtime filter to format Unix timestamps in notifications (#3641) (#4503)

2026-10-07 16:24:24 +02:00

regex.py

Notifications - |regex_replace ReDoS timeout now works in any thread (use 'regex' package timeout=) (#4585)

2026-10-23 15:31:51 +02:00