-
Notifications
You must be signed in to change notification settings - Fork 747
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(devSrv): Do not fail connection if a client processor fails #19209
Conversation
5902fcf
to
5b709ed
Compare
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-19209/index.html |
|
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-19209/index.html |
|
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-19209/index.html |
🤖 Your WebAssembly Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-19209/index.html |
The build 151860 found UI Test snapshots differences: Details
|
Bugfix
Do not fail connection if a client processor initialization fails
What is the current behavior?
If a client processor fails (like HR client if not properly configured), then connection to the dev-server is not initialized properly.
What is the new behavior?
PR Checklist
Screenshots Compare Test Run
results.