-
Notifications
You must be signed in to change notification settings - Fork 0
Harden API port handling and startup logging #2
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
Open
Maliot100X
wants to merge
2
commits into
main
Choose a base branch
from
tinyagi/runtime-hardening-1
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
@hono/node-server serve function error handling EADDRINUSE💡 Result:
The EADDRINUSE error in
@hono/node-server's serve function occurs when attempting to bind to a port (default 3000) that is already in use by another process. This is a standard Node.js http.Server listen error, not specific to Hono. To handle it: 1. Identify and kill the process using the port: - macOS/Linux: lsof -i :3000 then kill -9 - Windows: netstat -ano | findstr :3000 then taskkill /PID /F - Or kill all Node processes: killall node (macOS/Linux) or taskkill /F /IM node.exe (Windows) 2. Use a different port: import { serve } from '@hono/node-server' import { Hono } from 'hono' const app = new Hono serve({ fetch: app.fetch, port: 3001 // or process.env.PORT || 3000 }) 3. For graceful handling, capture the returned server and add an error listener: const server = serve({ fetch: app.fetch, port: 3000 }) server.on('error', (err) => { if (err.code === 'EADDRINUSE') { console.error(Port 3000 is already in use. Try a different port.) process.exit(1) } }) No built-in EADDRINUSE handling exists in serve options per official docs. Hono's app.onError handles route-level errors, not server bind errors.Citations:
🏁 Script executed:
Repository: Maliot100X/ZooBot
Length of output: 584
🏁 Script executed:
Repository: Maliot100X/ZooBot
Length of output: 366
🏁 Script executed:
Repository: Maliot100X/ZooBot
Length of output: 43
🏁 Script executed:
Repository: Maliot100X/ZooBot
Length of output: 43
🏁 Script executed:
Repository: Maliot100X/ZooBot
Length of output: 116
🏁 Script executed:
Repository: Maliot100X/ZooBot
Length of output: 137
🏁 Script executed:
Repository: Maliot100X/ZooBot
Length of output: 43
🏁 Script executed:
Repository: Maliot100X/ZooBot
Length of output: 827
🏁 Script executed:
Repository: Maliot100X/ZooBot
Length of output: 2236
Add error handler for async port binding failures.
The
serve()function from@hono/node-serverreturns synchronously, but the actual port binding happens asynchronously. The try/catch only catches synchronous errors like invalid port validation fromresolveApiPort().If the port is already in use (EADDRINUSE), the error will emit as an
'error'event on the server object and won't be caught by this try/catch, causing an unhandled exception.🔧 Proposed fix
let apiServer: http.Server; try { apiServer = startApiServer(); + apiServer.on('error', (err: NodeJS.ErrnoException) => { + log('ERROR', `API server error: ${err.message}`); + if (err.code === 'EADDRINUSE') { + log('ERROR', `Port already in use`); + } + process.exit(1); + }); } catch (error) { log('ERROR', `Failed to start API server: ${(error as Error).message}`); process.exit(1); }📝 Committable suggestion
🤖 Prompt for AI Agents