Subhra264 659a5439d1 fix: Make cron handler DST aware (#8952) ...

# Add DST-Aware Timezone Handling for Alert Scheduling

## Summary
Alerts previously used static timezone offsets that became outdated
during DST transitions, causing alerts to fire at incorrect times (e.g.,
an alert configured for "9 AM Pacific" would fire at 10 AM after DST
change).

## Solution
- Added `chrono-tz` dependency for IANA timezone database support
- Implemented DST-aware offset calculation at scheduling time using
timezone strings (e.g., `America/Los_Angeles`)
- Updated `get_next_trigger_time_non_aligned()` and `align_time()` to
dynamically calculate offsets based on the scheduled timestamp
- Maintains backward compatibility: alerts without timezone strings
continue using fixed offsets

2025-11-05 10:42:51 +05:30

..

api-testing

fix: UI design implementation (#8841)

2025-11-01 21:22:27 +05:30

test-data

test: Cleanup Mechanism and ENV Runs for e2e tests (#8839)

2025-11-04 23:54:54 +05:30

ui-testing

test: Cleanup Mechanism and ENV Runs for e2e tests (#8839)

2025-11-04 23:54:54 +05:30

input.json

docs: Fix typos (#4492)

2024-09-22 17:57:47 +08:00

integration_test.rs

fix: Make cron handler DST aware (#8952)

2025-11-05 10:42:51 +05:30

saveviews.json

chore: fix frontend typos (#4612)

2024-09-25 11:09:26 +08:00

trace_input.json

feat: new search engine (#4182)

2024-09-20 15:10:54 +08:00