-
Notifications
You must be signed in to change notification settings - Fork 929
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
Restore dialog broken #23257
Comments
In my test environment I am able to open the restore dialog from the Manage dashboard, as a workaround. I get the below exception when launching from OE.
|
The only change in the linked PR was to move a part of function in a separate function. Adding the moved code to original function seems to resolve the error (but we also need the new function for commanLine use, so code would be duplicated.. we should look for a better solution long term). The issue seems that the new function is not available when called from OE.. Does it mean OE is casting to a base type and is hiding functionalities from original type? We should also a test case that tests both types function list is identical (if that's intended) and not just the options key - as they are not interchangeable. We aren't able to add any new functions (private also doesn't work) to ProviderConnectionInfo independently until this design is fixed, otherwise we would continue facing this kind of issue from any part of the application. |
@cheenamalhotra The issue was caused by this line : https://github.com/microsoft/azuredatastudio/pull/23104/files#diff-f952231bc3fde12d411ad32e4e9fd058ae7127e1516fb230e077106f55fe858fR205 See the original PR for why this breaks it (tl;dr, the "this" context is incorrect when the object is converted to an IConnectionProfile) |
Fix has been ported to hotfix branch. |
Verified fixed in latest RC1 Version: 1.44.1-rc1 (user setup) |
1.44/Insiders
Same issue as #22839, which was fixed in #22840
The problem was reintroduced in #23104
I had added a test in the original fix that would have caught this, but unfortunately that was removed in a later PR that reverted the entire original feature : https://github.com/microsoft/azuredatastudio/pull/22997/files#diff-1f7cb57d04746810c6a813556ea08b667478f91cb7598f607d819cbe155d805eL287
The text was updated successfully, but these errors were encountered: