-
Notifications
You must be signed in to change notification settings - Fork 820
fix: Fix possible invalid error message #21623
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR fixes an issue where the VS extension logs an invalid timeout error message when the dev-server takes longer than expected to connect back to the IDE. The root cause was that the IDE channel was being initialized too late in the dev-server startup process (after add-ins resolution), causing the VS extension to timeout prematurely.
Key Changes:
- Increased the connection timeout threshold from 5 seconds to 10 seconds in the VS extension
- Moved IDE channel initialization earlier in the dev-server startup sequence to occur before add-in resolution
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
src/Uno.UI.RemoteControl.VS/EntryPoint.cs |
Doubled the timeout delay from 5 to 10 seconds with clarifying comment |
src/Uno.UI.RemoteControl.Host/Program.cs |
Moved IDE channel registration and initialization from host services to global services, enabling earlier connection |
src/Uno.UI.RemoteControl.Host/IDEChannel/IdeChannelServer.cs |
Added comment clarifying keep-alive timing expectations |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-21623/docs/index.html |
|
🤖 Your WebAssembly Skia Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-21623/wasm-skia-net9/index.html |
|
|
9afdcf1 to
45d8959
Compare
|
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-21623/docs/index.html |
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.
|
🤖 Your WebAssembly Skia Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-21623/wasm-skia-net9/index.html |
|
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-21623/docs/index.html |
|
|
ccf984b to
93cf7ab
Compare
|
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-21623/docs/index.html |
|
🤖 Your WebAssembly Skia Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-21623/wasm-skia-net9/index.html |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-21623/docs/index.html |
|
🤖 Your WebAssembly Skia Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-21623/wasm-skia-net9/index.html |
|
The build 179093 found UI Test snapshots differences: Details
|
|
|
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
🤖 Your WebAssembly Skia Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-21623/wasm-skia-net9/index.html |
|
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-21623/docs/index.html |
|
The build 179209 found UI Test snapshots differences: Details
|
|
|
closes #21622
🐞 Bugfix
Possible invalid error message in logs / output
What is the current behavior? 🤔
The dev-server connects back to the IDE only once it's fully setup, including after the add-ins has been resolved, which might take a while. This drives the VS extension to assume something went wrong as it didn't get any news from the dev-server in the given delay.
What is the new behavior? 🚀
IDE channel is enable much earlier.
PR Checklist ✅
Screenshots Compare Test Runresults.