davsclaus opened a new pull request, #24133:
URL: https://github.com/apache/camel/pull/24133

   ## Summary
   
   _Claude Code on behalf of Claus Ibsen_
   
   Upgrade TamboUI from 0.3.0 to 0.4.0 and remove workarounds that are no 
longer needed:
   
   - **Delete custom `MirroredSparkline`** (456 lines) — replaced by upstream 
`DualSparkline` widget now available in TamboUI 0.4. All 4 usages in 
`CircuitBreakerTab` and `EndpointsTab` migrated.
   - **Remove reflection hack** in `TuiBackendHelper` — the 
`JLineBackend(Terminal)` constructor is now public API, replacing the 
reflection probe + fallback pattern.
   - **Remove class preloading workaround** — deleted 
`TuiHelper.preloadClasses()` and its call sites in `CamelMonitor` and 
`CamelCatalogTui`. TamboUI 0.4's built-in shutdown hook and macOS terminal 
close fix handle clean shutdown without needing eager class loading.
   
   ### What's kept (still needed)
   - `Signal.handle("INT")` — still needed to exit the TUI run loop on Ctrl+C 
(TamboUI's shutdown hook restores terminal state but doesn't call `quit()`)
   - `fixControlChars()` — tab-to-8-spaces expansion is still useful (TamboUI 
replaces tabs with single space)
   - `buffer.clear(area)` before tab rendering — no specific fix for the buffer 
diff bleed-through issue in 0.4
   
   ## Test plan
   - [ ] Build passes: `mvn install -DskipTests` in `camel-jbang-plugin-tui`
   - [ ] Run `camel monitor` and verify sparkline charts render correctly on 
Endpoints and Circuit Breaker tabs
   - [ ] Verify tab switching does not show styled cell bleed-through
   - [ ] Verify Ctrl+C exits cleanly without ClassNotFoundException stack traces
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   
   Co-Authored-By: Claude Opus 4.6 <[email protected]>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to