-
Notifications
You must be signed in to change notification settings - Fork 459
fix(SSE): only initialize http.Server
when not set
#229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
WalkthroughThe Changes
Possibly related issues
Possibly related PRs
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🔇 Additional comments (1)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Fix issue #156
Currently, func
SSEServer.Start()
always resetsSSEServer.http.Server
, which may prevent us from customizing the process logic ofSSEServer.http.Server
when we call funcNewSSEserver()
with SSEOption argument of typeWithHTTPServer
This PR enhances func
SSEServer.Start()
in following aspects:http.Server
when it is not obviously set by userhttp.Server.Addr
if it is not set in funcWithHTTPServer
WithHTTPServer
is not consistent with funcStart
's argumentSummary by CodeRabbit