mirror of
https://github.com/unraid/api.git
synced 2026-01-06 16:49:49 -06:00
42406e795d
so the parser does not treat them as comments. This surfaces a new bug: `#`'s in notification subject or descriptions are treated as comments, and content following a `#` will not be displayed in queries from the api, unless the values are explicitly quoted as strings: ``` subject=Warning #1 OS # ❌ Truncates after "Warning" subject=\#1 OS # ❌ Backslash escape doesn't work subject="Warning #1 OS" # ✅ Double quotes work! subject='Warning #1 OS' # ✅ Single quotes work! ``` <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## Version 4.25.3 * **Improvements** * Enhanced notification system with improved handling of special characters and HTML-formatted content in messages. * Better text rendering accuracy across all notification types. * **Chores** * Updated application dependencies. * Version bumped to 4.25.3. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
7 lines
435 B
Plaintext
7 lines
435 B
Plaintext
timestamp=1730937600
|
|
event=Temperature Test
|
|
subject=Warning [UNRAID] - High disk temperature detected: 45 °C
|
|
description=Disk 1 temperature has reached 45 °C (threshold: 40 °C)<br><br>Current temperatures:<br>Parity - 32 °C [OK]<br>Disk 1 - 45 °C [WARNING]<br>Disk 2 - 38 °C [OK]<br>Cache - 28 °C [OK]<br><br>Please check cooling system.
|
|
importance=warning
|
|
|