Skip to content

Hawk's llama-server is the one on its port - #16

Merged
ChakraFusion merged 1 commit into
mainfrom
fix/llama-by-port
Oct 6, 2026
Merged

ChakraFusion merged 1 commit into
mainfrom
fix/llama-by-port

Conversation

@ChakraFusion

Copy link
Copy Markdown
Owner

Users may run several llama-server instances by hand; Hawk must only start (and stop) its own. Hawk took the first llama-server.exe from tasklist. Now it uses the process listening on llama_api_port; a server Hawk just started counts for 3 minutes while it loads (no second start); the name lookup remains only as a fallback when listeners cannot be read, and only if exactly one llama-server runs.

Tests: llama_by_port (two instances, loading grace, ambiguous fallback), 63/63.

🤖 Generated with Claude Code

… left alone

Hawk took the first llama-server.exe in tasklist: with a second instance started
by the user it could read the wrong one as alive or stop it on a restart. Now:
the process listening on llama_api_port; a server Hawk started in the last
3 minutes that is not listening yet still counts (no second start while it
loads); the name lookup only as a fallback and only when it is unambiguous.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ChakraFusion
ChakraFusion merged commit f62cf18 into main Oct 6, 2026
8 checks passed
@ChakraFusion
ChakraFusion deleted the fix/llama-by-port branch October 6, 2026 16:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant