Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: trigger refresh from client on hotswap with PUSH (#20848) (CP: 24.6) #20886

Merged
merged 1 commit into from
Jan 20, 2025

Conversation

vaadin-bot
Copy link
Collaborator

No description provided.

* fix: trigger refresh from client on hotswap with PUSH

When PUSH is enabled, Flow Hotswapper uses it to refresh only the affected UIs.
However, this can cause issues if Flow views contain code that relies on
VaadinRequest thread local, since hotswap refresh start in a background thread.
This change defines a client side event listener to trigger the refresh,
and uses PUSH only to fires the event.

Fixes #20843

* fix test
@vaadin-bot
Copy link
Collaborator Author

This PR is eligible for auto-merging policy, so it has been approved automatically. If there are pending conditions, auto merge (with 'squash' method) has been enabled for this PR[Message is sent from bot]

@vaadin-bot vaadin-bot enabled auto-merge (squash) January 20, 2025 15:23
Copy link

Test Results

1 161 files  ± 0  1 161 suites  ±0   1h 35m 59s ⏱️ - 3m 27s
7 583 tests ± 0  7 527 ✅ ± 0  56 💤 ±0  0 ❌ ±0 
7 952 runs  +51  7 887 ✅ +51  65 💤 ±0  0 ❌ ±0 

Results for commit 2f28b7b. ± Comparison against base commit 62def54.

@vaadin-bot vaadin-bot merged commit 6115df3 into 24.6 Jan 20, 2025
25 of 26 checks passed
@vaadin-bot vaadin-bot deleted the cherry-pick-20848-to-24.6-1737386161779 branch January 20, 2025 15:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants