linagora
OSS
ToM-server
Sign in / Sign up
Open main menu
ToM-server
GitHub
Overview
Runs
Analytics
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Succeeded
cs-bridge/feat/graceful-degradation
8f2d8d59 feat(cs-bridge): improve graceful degradation with timeout and runtime error detection - Add 30-second timeout for database connection at startup - Separate DB error handling from profile update error handling - DB read operations in try/catch (switches to degraded mode on error) - Profile updates outside try/catch (errors propagate normally) - DB save operations in separate try/catch (non-blocking) - Track profileUpdated flag to avoid double-processing on DB errors
6 days ago
by pm-McFly
p
Succeeded
cs-bridge/feat/graceful-degradation
d117fb4b style(cs-bridge): format bridge.ts
6 days ago
by pm-McFly
p
Succeeded
cs-bridge/feat/graceful-degradation
1efef42a feat(cs-bridge): add graceful degradation for database unavailability - Add #isDatabaseAvailable state tracking to CommonSettingsBridge - Wrap database initialization in try/catch with graceful fallback - Add degraded mode handling in #handleMessage - When database is unavailable: - Bridge continues to process messages - Idempotency and version checks are skipped - Updates are applied directly to Matrix profiles - Clear warning logs indicate degraded operation This allows the bridge to remain functional even when the database is temporarily unavailable, at the cost of duplicate processing.
6 days ago
by pm-McFly
p
Previous page
Previous
Next
Next page