Feat/bot leaderboard/v2.3

[lsabor]

No description provided.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: b6816165-2865-4f7c-a3cd-b6cc32b9e52f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/bot-leaderboard/v2.3

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

🚀 Preview Environment

Your preview environment is ready!

Resource	Details
🌐 Preview URL	https://metaculus-pr-4435-feat-bot-leaderboard-v2-3-preview.mtcl.cc
📦 Docker Image	ghcr.io/metaculus/metaculus:feat-bot-leaderboard-v2.3-842c814
🗄️ PostgreSQL	NeonDB branch preview/pr-4435-feat-bot-leaderboard-v2-3
⚡ Redis	Fly Redis mtc-redis-pr-4435-feat-bot-leaderboard-v2-3

Details

• Commit: 4ce24ff8f19705f8ccf55af9b703d301a8ac39ec
• Branch: feat/bot-leaderboard/v2.3
• Fly App: metaculus-pr-4435-feat-bot-leaderboard-v2-3

---

ℹ️ Preview Environment Info

Isolation:

• PostgreSQL and Redis are fully isolated from production
• Each PR gets its own database branch and Redis instance
• Changes pushed to this PR will trigger a new deployment

Limitations:

• Background workers and cron jobs are not deployed in preview environments
• If you need to test background jobs, use Heroku staging environments

Cleanup:

• This preview will be automatically destroyed when the PR is closed

[lsabor]

Nothing looked out of place to me in what @colesussmeier added. I'm the initial author, so I can't approve, but feel free to merge as is or address the tiny nit I added.

[lsabor]

Nit: I would avoid conditionally returning different structure outputs. just return tuple[float, float | None], only populating the second float conditionally