Skip to content

Fix vix health reporting healthy state after curl timeout #407

@GaspardKirira

Description

@GaspardKirira

Problem

vix health can currently display Healthy: yes even when the HTTP check failed with a curl timeout.

This is confusing because the final status says the service is healthy while the actual request failed.

Example behavior:

Healthy: yes
curl: timeout

Expected behavior

If the HTTP request times out, the health command should clearly report the check as failed.

Expected output should be closer to:

Healthy: no
Error: curl timeout

or:

Status: failed
Reason: request timed out

What to fix

The health result should not be marked as healthy unless the response was successfully received and validated.

The logic should separate:

  • service process status
  • HTTP response status
  • curl/network errors
  • timeout errors
  • response parsing errors

A timeout must always make the HTTP health check fail.

Goal

Make vix health local and vix health public reliable and avoid false positive health reports.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: cliCLI systemscope:cliCLI (vix run, vix dev, etc.)type: bugSomething is brokenuxUser experience improvements: CLI output, help formatting, readability, and usability.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions