fix: populate null fields in /api/status and fix n8n health detection#765
Merged
Lightheartdevs merged 1 commit intoLight-Heart-Labs:mainfrom Apr 3, 2026
Conversation
- Populate model.tokensPerSecond from llama metrics instead of null - Use system uptime for healthy services instead of null - Add disk usage and system info to /api/status response and fallback - Fix n8n health check to reuse shared HTTP session with longer timeout - Update all n8n-related tests to mock helpers._get_aio_session Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What
Populate previously-null fields in
/api/statusresponse and fix n8n health check returning false negatives.Why
model.tokensPerSecondwas hardcoded tonulldespite llama metrics being fetched in the same requestuptimevalues werenulldiskandsystemkeys were missing from the responsecheck_n8n_available()created a new HTTP session with 3s timeout per call, causing false negatives when n8n was slow to respondHow
model.tokensPerSecondfrom already-fetched llama metrics datacontext_sizefrom llama-server/propswhen available forcontextLengthuptimeto system uptime for healthy services (pragmatic approximation)disk(fromget_disk_usage) andsystem(hostname + uptime) to response and error fallbackcheck_n8n_available()to reuse the shared HTTP session (30s timeout) fromhelpers._get_aio_session()helpers._get_aio_sessioninstead ofaiohttp.ClientSessionTesting
python -m py_compilepasses for all modified filesPlatform Impact
🤖 Generated with Claude Code