Repository navigation
fix: close off-request navigations, rate-limit per session, cap settings (#437) (CP: 5.0) - #446
Merged
Merged
Conversation
…ngs (#437) Close out a navigation started outside a request (UI.access, push) that never reaches afterNavigation from an access task on its own thread, so its scope is not left open on a pooled thread. Keep the client metrics rate limiter in the session, so all tabs of a session share the client-rate-per-session budget. Reject insightsCapacity, routeCardinalityLimit and databaseSpanLimit values above a fixed maximum. Related: #430
caalador
approved these changes
Oct 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR cherry-picks changes from the original PR #437 to branch 5.0.
Original PR description