Skip to content

fix: Fail on multiple executors only when the executor is accessed (#21839) (CP: 24.8) - #21844

Merged
vaadin-bot merged 1 commit into
24.8from
cherry-pick-21839-to-24.8-1751634960979
Jul 4, 2025
Merged

vaadin-bot merged 1 commit into
24.8from
cherry-pick-21839-to-24.8-1751634960979

Conversation

@vaadin-bot

Copy link
Copy Markdown
Collaborator

No description provided.

…21839)

Does not fail eagerly if a Spring app has multiple TaskExecutor bean (without VaadinTaskExecutor qualifier).
Instead it fails when an app tries to access VaadinService.getExecutor() directly or via using a feature that uses this executor (currently the signals preview).

Fixes #21811
@vaadin-bot

Copy link
Copy Markdown
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) July 4, 2025 13:22
@sonarqubecloud

sonarqubecloud Bot commented Jul 4, 2025

Copy link
Copy Markdown

@github-actions

github-actions Bot commented Jul 4, 2025

Copy link
Copy Markdown
Contributor

Test Results

1 236 files  ±0  1 236 suites  ±0   1h 13m 57s ⏱️ + 2m 5s
8 558 tests +2  8 502 ✅ +2  56 💤 ±0  0 ❌ ±0 
8 963 runs  +8  8 898 ✅ +8  65 💤 ±0  0 ❌ ±0 

Results for commit 7827dea. ± Comparison against base commit 93a3bde.

@vaadin-bot
vaadin-bot merged commit 39e8dc8 into 24.8 Jul 4, 2025
@vaadin-bot
vaadin-bot deleted the cherry-pick-21839-to-24.8-1751634960979 branch July 4, 2025 13: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