feat(translation-review): invite-token auth for collector saves#2913
Conversation
The shared collector requires a per-reviewer Bearer invite token for /submit and /suggest; the ui-react rebuild sent none, so saves 401'd. This wires the invite flow into the app. - Consume a #token=... invite fragment on load: store it locally, then strip it from the URL so the secret is not left in history or shared by copy-paste. - Send Authorization: Bearer on submit and suggest when a token is present. - On a 401, clear the stored token and prompt the reviewer to open their invite link; edits stay local meanwhile. - Show a hint when the collector is reachable but no invite token is present. - Tests: token sent + stripped, 401 prompt, connected-without-token hint. Reads (status/progress) stay anonymous; only writes need the token. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LfG2AV7RQC3ncBLB9ApLAE
|
Warning Review limit reached
Next review available in: 4 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
✨ 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 |
…oken With the collector now live, saving/suggesting from a device that has no invite token 401'd — handled gracefully in the UI, but the browser still logged the 401 as a console error. Short-circuit both paths: when no token is present, show the "open your invite link" prompt (save) or reset the button (suggest) without hitting the server. Only a genuinely invalid/revoked token can now log a single 401, which self-corrects (the handler clears it). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LfG2AV7RQC3ncBLB9ApLAE
The bottom (utility) panel had grown to four stacked rows (~120-168px) with a lot of blank space. Redesign it as a one-row status bar and pin the panel to that height so toggling it open shows exactly one row. - Collapse the header/row/session/keys stack into a single flex row inside a .status-strip__bar child (avoids fighting the shell region's column layout): collector state · last saved · today's session · progress waterline — then a spacer — keyboard hints · build. Dot separators between left-cluster items. - Progressive disclosure by width: drop keyboard hints (≤64rem), build (≤48rem), session (≤30rem); collector state + saved + waterline always stay. - The shell enforces a ~120px utility floor; override it (scoped to this status strip) so the panel hugs the ~34px bar in both overlay and docked layouts. panelSizes.utility set to match. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LfG2AV7RQC3ncBLB9ApLAE
1 participant
Why
The translation collector requires a per-reviewer Bearer invite token for
/submitand/suggest(there's anissue/revokeinvite model; submissions are attributed to a reviewer with atrustlevel). The ui-react rebuild (#2710) shipped no token flow, so saving against a live collector 401'd. This wires the invite flow into the app so shared dogfooding works.What
#token=…invite fragment on load: store it locally, then strip it from the URL so the secret isn't left in history or shared by copy-paste.Authorization: Bearer <token>on/submitand/suggestwhen a token is present.Reads (
/status, progress) stay anonymous; only writes need the token.Verified end-to-end
Stood up the collector on winhub (tailnet-only, CORS-scoped, scheduled-task persistence) and confirmed against the live preview:
reviewer: CIC,trust: untrusted).Access-Control-Allow-Origin.Gates:
pnpm typecheckclean,pnpm test21/21.🤖 Generated with Claude Code