fix(llc): fix userId for guest#128
Conversation
|
Warning Review limit reached
Next review available in: 55 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: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAuthInterceptor now populates ChangesAuthenticated request identity
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #128 +/- ##
==========================================
+ Coverage 45.80% 46.19% +0.38%
==========================================
Files 178 178
Lines 7243 7243
==========================================
+ Hits 3318 3346 +28
+ Misses 3925 3897 -28 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
| // Use the resolved token's own user id rather than | ||
| // `_tokenManager.userId`: some token providers (e.g. guest exchanges) | ||
| // can resolve to a different id than the one originally requested, and | ||
| // this must stay consistent with the identity in the `Authorization` | ||
| // header below. | ||
| options.queryParameters['user_id'] = token.userId; |
There was a problem hiding this comment.
In my opinion the token should always match the id set in the token manager. if its different we should expire the current token and get a new token for the user id set in the manager.
There was a problem hiding this comment.
We already throw an error if the loaded token mismatches the user id.
Submit a pull request
Linear: FLU-373
CLA
Description of the pull request
When logging in as guest user the backend generates a userId for you. That's in the token, but not available when constructing the tokenManager. By getting it from the token directly we are always sure to have the right user id.
Neede for: GetStream/stream-feeds-flutter#113
Summary by CodeRabbit
Bug Fixes
Tests