ruvnet/RuView · error · HTTPException

An internal error occurred. Please try again later.

Error message

An internal error occurred. Please try again later.

What it means

Generic HTTP 500 from POST /pose/estimate when pose_service.estimate_poses raises anything. The handler hides the cause from the client ('An internal error occurred') but logs 'Error in pose estimation: <e>' server-side, so the log is the only place with the real reason. Root causes are service-state problems: model not loaded, empty CSI frame buffer, or unknown zone ids.

Source

Thrown at archive/v1/src/api/routers/pose.py:138

):
    """Get current pose estimation from WiFi signals."""
    try:
        logger.info(f"Processing pose estimation request from user: {current_user.get('id') if current_user else 'anonymous'}")
        
        # Get current pose estimation
        result = await pose_service.estimate_poses(
            zone_ids=request.zone_ids,
            confidence_threshold=request.confidence_threshold,
            max_persons=request.max_persons,
            include_keypoints=request.include_keypoints,
            include_segmentation=request.include_segmentation
        )
        
        return PoseEstimationResponse(**result)
        
    except Exception as e:
        logger.error(f"Error in pose estimation: {e}")
        raise HTTPException(
            status_code=500,
            detail="An internal error occurred. Please try again later."
        )


@router.post("/analyze", response_model=PoseEstimationResponse)
async def analyze_pose_data(
    request: PoseEstimationRequest,
    background_tasks: BackgroundTasks,
    pose_service: PoseService = Depends(get_pose_service),
    current_user: Dict = Depends(require_auth)
):
    """Trigger pose analysis with custom parameters."""
    try:
        logger.info(f"Custom pose analysis requested by user: {current_user['id']}")
        
        # Trigger analysis
        result = await pose_service.analyze_with_params(

View on GitHub (pinned to 4685618388)

Solutions

1. Read the server log — the 'Error in pose estimation:' line names the actual exception
2. Verify readiness (model loaded, CSI data flowing) via /health or /ready before estimating
3. Validate zone_ids against known zones first
4. If it is warm-up related and transient, retry once after a short delay

Example fix

# before
resp = await client.post('/pose/estimate', json=body)
resp.raise_for_status()

# after
for attempt in range(3):
    resp = await client.post('/pose/estimate', json=body)
    if resp.status_code != 500:
        break
    await asyncio.sleep(2 ** attempt)
resp.raise_for_status()

ready = (await client.get('/ready')).json().get('ready', False)
if not ready:
    raise ServiceNotReady('wait for model load + CSI data before estimating')

last_exc = None
for attempt in range(3):
    try:
        resp = await client.post('/pose/estimate', json=body)
        resp.raise_for_status()
        return resp.json()
    except httpx.HTTPStatusError as e:
        if e.response.status_code != 500 or attempt == 2:
            raise
        await asyncio.sleep(2 ** attempt)

When it happens

Trigger: POST /pose/estimate with zone_ids the service does not know, or while the service is not warm (model not loaded, no CSI frames ingested yet) — estimate_poses raises and the handler converts it to the generic 500.

Common situations: Starting the API before model weights are loaded; calling estimation before any CSI data flows from the firmware node; hardware not attached in real-hardware mode so the frame buffer stays empty.

Related errors

• Health check failed: {str(e)}
• Failed to get system metrics: {str(e)}
• An internal error occurred. Please try again later.
• brain line ${index + 1}: exceeds 16 KiB
• JWT authentication is not configured. In development mode, e

AI-assisted analysis of ruvnet/RuView@4685618388 (2026-08-16). Data as JSON: /api/errors/b0210cd67b362bd1. Report an issue: GitHub.