Skip to content

Conversation

@ad-astra-video
Copy link
Contributor

Fix to send back 503 response if current_client is set.

Also updates to send back current_state in response

Copy link
Collaborator

@eliteprox eliteprox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change looks good to me. Tested solution resolves the primary issue of interrupting an active stream with a start request.

There is an existing defect that make the status response inaccurate though. This is a universal issue with even /stream/status endpoint. We can address it in a follow-up PR https://github.com/livepeer/pytrickle/tree/fix-get-pipeline-state

{
    "status": "error",
    "message": "Pipeline is still in use",
    "current_state": {
        "status": "OK",
        "state": "OK",
        "error_message": null,
        "pipeline_ready": true,
        "active_streams": 1,
        "startup_complete": true,
        "pipeline_state": "IDLE",
        "additional_info": {}
    }
}

@eliteprox eliteprox linked an issue Dec 10, 2025 that may be closed by this pull request
@ad-astra-video ad-astra-video merged commit ae57b62 into main Dec 10, 2025
4 checks passed
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.

Start request during active stream stops running client/stream

3 participants