F-Kamp

After updating to Vaadin 24.7.4 the bug still occurs. I've also noticed that running the tests in sequence instead of fully parallelized seems to reduce the likelihood of triggering this...

I've configured the push mechanism by adding the annotation `@Push` on a class that inherits from `AppShellConfigurator` without specifying anything explicitly, so it should use the default values(`PushMode.AUTOMATIC` and `Transport.WEBSOCKET_XHR`)...

I've further analyzed the lazy loading behavior. There was a small bug in our code that triggered the eager instance creation. I've fixed that. The `Unexpected message id from the...

Feel free to ask everything - no, we don't touch anything from `UIInternals`.

I don't mind testing it with a prerelease version, but I'm not sure if I can get the console logs. The only reliable way to trigger this bug was to...

We are using the Vaadin Testbench with Selenium for E2E tests. I didn't know about the `driver.manage().logs()` API, so thanks for the pointer! The `frontendHotdeploy` doesn't work with our setup...

I've executed the tests a few times by now. I do not receive the `Unexpected message id from the client` exception anymore, but some warnings remain. Here is an excerpt...

> About the `old duplicate message` there's definitely something wrong here, because it seems that the client never processes response to message 15, so it continues to send it to...

After adding the snippet above, I can see the following entries in the log file: ``` [2025-06-02T06:13:37.611Z] [WARNING] http://[IP (removed by FKamp)]:8080/SynapticaOS/VAADIN/build/FlowClient-DyMGXbet.js 0:8192 "Gave up waiting for message 19 from...

Thank you for bearing with me. Here are the complete browser logs: [browser.log](https://github.com/user-attachments/files/20550572/browser.log) And the ServerRpcHandler logs: [ServerRpcHandler.log](https://github.com/user-attachments/files/20550577/ServerRpcHandler.log)