Skip to content

feat: Add process state to /upstream #135

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 16, 2025

Conversation

fakezeta
Copy link
Contributor

@fakezeta fakezeta commented May 16, 2025

This PR adds information about the process for model right after the model name in the HTML page created by /upstream

Summary by CodeRabbit

  • New Features
    • The model listing page now displays the current state of each model (e.g., Ready, Starting, Stopping, Failed, Shutdown) next to its link for improved visibility.

Copy link

coderabbitai bot commented May 16, 2025

Walkthrough

The upstreamIndex handler in proxy/proxymanager.go was updated to display the current state of each model's process alongside its link in the HTML output. The handler now retrieves, maps, and appends a human-readable process state for each model in the generated list.

Changes

File(s) Change Summary
proxy/proxymanager.go Modified the upstreamIndex handler to append each model's process state to its link in HTML output.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant ProxyManager
    participant ProcessGroup
    participant Process

    User->>ProxyManager: Request upstream index
    ProxyManager->>ProxyManager: Retrieve and sort model IDs
    loop For each model ID
        ProxyManager->>ProcessGroup: Find process group for model
        ProcessGroup-->>ProxyManager: Return process group (if exists)
        ProxyManager->>Process: Find process for model
        Process-->>ProxyManager: Return process (if exists)
        ProxyManager->>Process: Get current state
        Process-->>ProxyManager: Return state (e.g., Ready, Starting)
        ProxyManager->>ProxyManager: Map state to human-readable string
        ProxyManager->>ProxyManager: Append model link and state to HTML
    end
    ProxyManager-->>User: Return HTML with model links and states
Loading

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.

✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
proxy/proxymanager.go (1)

337-361: Good addition of process state information, but consider handling nil cases

The implementation nicely displays process state alongside model names, making it easier for users to understand the current status of each model. The mapping from internal state constants to human-readable strings is well done with a proper default case.

However, when a process group or process doesn't exist for a model ID, the code will display " - " (dash with empty state) in the HTML. Consider initializing the state variable with a default value like "Not Running" to provide more clarity in these cases.

 		var state string = "Not Running"  // Default state when process doesn't exist
 		if processGroup != nil {
 			process := processGroup.processes[modelID]
 			if process != nil {
 				var stateStr string
 				switch process.CurrentState() {
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between afc9aef and f04c18f.

📒 Files selected for processing (1)
  • proxy/proxymanager.go (1 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
proxy/proxymanager.go (1)
proxy/process.go (5)
  • StateReady (23-23)
  • StateStarting (22-22)
  • StateStopping (24-24)
  • StateFailed (27-27)
  • StateShutdown (30-30)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: run-tests

@mostlygeek mostlygeek merged commit 2d00120 into mostlygeek:main May 16, 2025
3 checks passed
@mostlygeek
Copy link
Owner

thanks!

@fakezeta fakezeta deleted the process_state branch May 16, 2025 15:02
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.

2 participants