fix: report TLS from active channel handlers - #1011
Conversation
|
Warning Review limit reached
Next review available in: 33 minutes Limit details: You’ve used all 3 included reviews currently available. Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?Wait for the limit to reset, then comment An organization admin can change what happens after included review limits in Billing. How do review limits work?CodeRabbit enforces per-developer PR review limits within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: QUIET Plan: Pro Plus Run ID: 📒 Files selected for processing (7)
Comment |
Moves active-channel TLS detection out of #999.
The configuration report now derives whether TLS is enabled from the control channel pipeline after
NettyOptions.afterChannelInitialized, so custom hooks that add or remove anSslHandlerare reflected accurately. Hostname-verification behavior is otherwise unchanged.Tests:
mvn -pl core -DskipITs -Dtest=DefaultDriverConfigReporterTest,ProtocolInitHandlerTest test