Conversation
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 18 minutes and 23 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughrefactors internal token retrieval: Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@hub_adapter/auth.py`:
- Line 163: The signature of _get_internal_token was changed to remove the
oidc_config parameter, but existing callers still pass (oidc_config, settings)
causing a TypeError; either update each caller to call
_get_internal_token(settings) (remove the oidc_config argument) where referenced
(e.g., callers in modules that invoke _get_internal_token) or add a short
compatibility shim named _get_internal_token that accepts (oidc_config,
settings) and forwards to the new async _get_internal_token(settings) (ignoring
or extracting what’s needed from oidc_config) so existing call sites keep
working until callers are updated.
- Around line 173-175: The code assumes settings.node_svc_oidc_url is always the
issuer base and blindly appends "/protocol/openid-connect/token" to build
int_token_ep; instead detect and normalize the issuer: if node_svc_oidc_url
contains "/.well-known/" take the substring before "/.well-known/" as the
issuer, otherwise use node_svc_oidc_url.rstrip('/'), then build int_token_ep =
issuer + "/protocol/openid-connect/token" and use that for httpx.post; update
references near int_token_ep, node_svc_oidc_url, and the httpx.post call to use
the normalized issuer.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 786ed00a-8103-4970-af64-ba72f3ec651b
📒 Files selected for processing (5)
hub_adapter/auth.pytests/conftest.pytests/constants.pytests/test_auth.pytests/test_oidc.py
Keep internal token fetching internal (within k8s)
Summary by CodeRabbit
Refactor
Tests