Skip to content

fix: close off-request navigations, rate-limit per session, cap settings (#437) (CP: 5.0) - #446

Merged
caalador merged 2 commits into
5.0from
cherry-pick-437-to-5.0-1791191070747
Oct 6, 2026
Merged

caalador merged 2 commits into
5.0from
cherry-pick-437-to-5.0-1791191070747

Conversation

@vaadin-bot

Copy link
Copy Markdown
Collaborator

This PR cherry-picks changes from the original PR #437 to branch 5.0.

Original PR description

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

…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
caalador merged commit 981e65a into 5.0 Oct 6, 2026
4 checks passed
@caalador
caalador deleted the cherry-pick-437-to-5.0-1791191070747 branch October 6, 2026 05:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants