Skip to content

Revert "fix(scheduling): query "/" to check if a runner is ready"#193

Merged
doringeman merged 1 commit intomainfrom
revert-170-wait-runner
Oct 3, 2025
Merged

Revert "fix(scheduling): query "/" to check if a runner is ready"#193
doringeman merged 1 commit intomainfrom
revert-170-wait-runner

Conversation

@doringeman
Copy link
Contributor

@doringeman doringeman commented Oct 3, 2025

Reverts #170

Summary by Sourcery

Bug Fixes:

  • Restore the HTTP readiness check to target "/v1/models" instead of the root path

Copilot AI review requested due to automatic review settings October 3, 2025 09:55
@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Oct 3, 2025

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR reverts the readiness probe change to query "/" and restores querying the "/v1/models" endpoint by updating the HTTP request URL.

File-Level Changes

Change Details Files
Revert readiness endpoint to "/v1/models"
  • Update URL in http.NewRequestWithContext from "/" to "/v1/models"
pkg/inference/scheduling/runner.go

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @doringeman, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses an issue by reverting a previous change that modified the readiness check mechanism for runners. The revert restores the original endpoint used to determine if a runner is operational, ensuring stability and correct behavior of the scheduling system.

Highlights

  • Revert Previous Change: This pull request fully reverts the changes introduced in docker/model-runner#170, effectively undoing a prior modification.
  • Readiness Check Endpoint: The endpoint used for checking if a runner is ready has been reverted from querying the root path (/) back to the more specific /v1/models.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR reverts a previous change that modified the endpoint used for checking runner readiness from /v1/models back to /. This revert undoes the fix that was implemented in PR #170.

  • Reverts the readiness check endpoint from "/" back to "/v1/models"

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@@ -205,7 +205,7 @@ func (r *runner) wait(ctx context.Context) error {
default:
}
// Create and execute a request targeting a known-valid endpoint.
Copy link

Copilot AI Oct 3, 2025

Choose a reason for hiding this comment

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

Reverting to /v1/models endpoint may reintroduce the original issue that PR #170 was intended to fix. Consider documenting why this revert is necessary and whether the underlying problem has been resolved through other means.

Suggested change
// Create and execute a request targeting a known-valid endpoint.
// Create and execute a request targeting a known-valid endpoint.
// NOTE: This readiness check uses the `/v1/models` endpoint.
// This was reverted to `/v1/models` following PR #170, which originally changed the endpoint
// to address [describe the issue, e.g., a bug, security, or compatibility problem].
// The underlying problem has been [resolved/mitigated] through [other means/changes], so reverting is safe.
// If the issue resurfaces, consider updating this endpoint and reviewing PR #170 for context.

Copilot uses AI. Check for mistakes.
Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey there - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request reverts a previous change that set the runner readiness check endpoint to /. As the root endpoint handler returns a 404, that change was likely causing readiness checks to fail. This revert restores the endpoint to /v1/models, which is a standard OpenAI API endpoint for listing models and is a more suitable target for a readiness probe. The change is correct and improves the reliability of the runner. I have one minor suggestion to improve maintainability.

}
// Create and execute a request targeting a known-valid endpoint.
readyRequest, err := http.NewRequestWithContext(ctx, http.MethodGet, "http://localhost/", http.NoBody)
readyRequest, err := http.NewRequestWithContext(ctx, http.MethodGet, "http://localhost/v1/models", http.NoBody)
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

For better maintainability and to avoid magic strings, it's a good practice to define this URL as a constant. For example, you could declare const readinessProbeURL = "http://localhost/v1/models" at the package level and use it here.

@doringeman doringeman merged commit 48bc7e2 into main Oct 3, 2025
5 checks passed
@doringeman doringeman deleted the revert-170-wait-runner branch October 3, 2025 09:59
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.

3 participants