fix(frontend): strip ANSI escape codes before parsing service status#51
Conversation
The backend injects ANSI color escape codes into some system status strings
(e.g., Bonding status). These escape codes were causing substring matches
(like `.includes('mptcp proxy (shadowsocks): active')`) to fail in the frontend
`parseServiceStatus` utility. This commit adds a regex replacement to strip
all ANSI escape codes from the `rawStatus` string before evaluation, ensuring
correct status state mapping (e.g., degraded/yellow instead of offline/gray).
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
Fix for frontend Bonding status parsing bug where ANSI escape codes from the backend were breaking the state evaluation, causing the indicator to show gray (offline) instead of yellow (degraded) or green (online).
PR created automatically by Jules for task 4927774518656227587 started by @viruslox