Skip to content

Updated judge execute and listing endpoints to match the new v1 syntax#26

Merged
TensorTemplar merged 3 commits intomainfrom
judges-api-update
Jun 30, 2025
Merged

Updated judge execute and listing endpoints to match the new v1 syntax#26
TensorTemplar merged 3 commits intomainfrom
judges-api-update

Conversation

@heljakka
Copy link
Collaborator

@heljakka heljakka commented Jun 29, 2025

Summary by CodeRabbit

  • Bug Fixes
    • Updated judge-related API endpoints to use the latest version for improved reliability.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 29, 2025

Walkthrough

The API endpoint paths in the RootSignalsJudgeRepository class were updated from the /beta/judges prefix to /v1/judges for judge-related operations. Only the endpoint URLs in the list_judges and run_judge methods were changed, with no other modifications to logic or control flow.

Changes

File(s) Change Summary
src/root_signals_mcp/root_api_client.py Updated judge-related API paths from /beta/judges to /v1/judges in two methods.

Poem

A bunny hopped from beta to v1,
Updating paths, its work nearly done.
Judges now live where the version is new,
The code is refreshed, the endpoints askew.
With a twitch of the nose and a satisfied grin,
The rabbit declares: let new judging begin!


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3218974 and 92904e8.

📒 Files selected for processing (1)
  • src/root_signals_mcp/root_api_client.py (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/root_signals_mcp/root_api_client.py
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: integration-tests
✨ 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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

@heljakka heljakka requested a review from TensorTemplar June 29, 2025 10:59
Copy link
Contributor

@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: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 658588a and 50540d1.

📒 Files selected for processing (1)
  • src/root_signals_mcp/root_api_client.py (2 hunks)
🧰 Additional context used
🪛 GitHub Actions: Integration Tests with Docker Compose
src/root_signals_mcp/root_api_client.py

[error] 406-414: Pre-commit hook 'ruff-format' failed: file was reformatted due to multi-line string concatenation changed to single line. Run 'pre-commit run --all-files' locally to reproduce and fix.

🔇 Additional comments (1)
src/root_signals_mcp/root_api_client.py (1)

484-487: Endpoint update looks correct

The execute path has been migrated to /v1/judges/{id}/execute/.
No other changes needed; signature and payload remain intact.

Styling fix

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Signed-off-by: Ari Heljakka <[email protected]>
Copy link
Contributor

@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: 1

♻️ Duplicate comments (1)
src/root_signals_mcp/root_api_client.py (1)

410-411: Convert boolean parameter to lowercase for API compatibility.

As previously noted, settings.show_public_judges is a Python boolean that will be converted to capitalized "True"/"False" in the URL string, but the API likely expects lowercase "true"/"false". Apply the fix suggested in the previous review to convert both the initial URL and url_params to use lowercase boolean strings.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 50540d1 and 3218974.

📒 Files selected for processing (1)
  • src/root_signals_mcp/root_api_client.py (2 hunks)
🧰 Additional context used
🪛 Ruff (0.11.9)
src/root_signals_mcp/root_api_client.py

410-410: SyntaxError: Expected ')', found '='

🪛 GitHub Actions: Integration Tests with Docker Compose
src/root_signals_mcp/root_api_client.py

[error] 410-410: SyntaxError: Expected ')', found '=' at line 410. Ruff linting failed due to this syntax error.


[error] 410-410: Ruff-format failed to parse file due to syntax error: Expected ')', found '=' at line 410.

🔇 Additional comments (1)
src/root_signals_mcp/root_api_client.py (1)

484-484: LGTM: Correct v1 API endpoint migration.

The endpoint path has been properly updated from /beta/judges to /v1/judges for the execute operation, which aligns with the PR objective to migrate to v1 syntax.

@heljakka heljakka requested a review from ogencoglu June 30, 2025 03:19
@TensorTemplar TensorTemplar merged commit bef7d36 into main Jun 30, 2025
2 checks passed
@TensorTemplar TensorTemplar deleted the judges-api-update branch June 30, 2025 05:56
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