Fix stale ViewerAsset capability URL in LLViewerAssetStorage on region teleports - #366
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
💤 Files with no reviewable changes (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughSummary by CodeRabbit
Walkthrough
ChangesViewer asset URL resolution
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: 🔵 Low · up to During a region teleport, asset requests may briefly fail if the new region has not finished providing its capability URL when the request resumes. The change is otherwise mergeable with explicit owner awareness and follow-up to recheck capability readiness after region changes. Poem
🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
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 |
Summary
LLViewerAssetStorage,mViewerAssetUrlwas cached as a member variable with anif (mViewerAssetUrl.empty())check.mViewerAssetUrlremained populated with the previous region's capability URL and was not updated to the new region'sViewerAssetcapability.AT_MATERIAL) and generic asset requests in the new region were sent using the old region's capability URL or direct unauthenticated CDN endpoints, failing with403 Forbidden/ missing asset errors.mViewerAssetUrlmember and dynamically queriesgAgent.getRegion()->getViewerAssetUrl()for every request inassetRequestCoro, matching the behavior ofLLMeshRepositoryandLLTextureFetch.