Anthony Iacono
Anthony Iacono
@erich-wang We deleted both msal.cache and wiped the keychain with no luck. Also tried sudo.
@bgavrilMS Just a quick reminder, we are on Mac and we are also affected by this issue.
@bgavrilMS I don't believe so. Here is a stack trace from Mac if that helps: ``` PS /Users/anthonyiacono> Connect-AzAccount -Debug DEBUG: 12:15:50 PM - ConnectAzureRmAccountCommand begin processing with ParameterSet 'UserWithSubscriptionId'....
I can do that, but they seem highly related even with slightly different stack traces.
I'm a little confused -- even after updating to 0.81.0, `npm audit` shows the high vunerability in `d3-color`: ``` npm audit # npm audit report d3-color =0.47.0 Depends on vulnerable...
> It seems like some other d3 packages are installing a different version, but you shouldn't pin all d3 packages to the latest version manually (or at your own risk...
What happens if you use the resourceId helper rather than “testbugstorage” inside depends on?
+1 For this feature. I tried out Clocal, but it doesn't look like it actually supports the same REST API as Azure KeyVault. @XiaoningLiu, would you mind sharing some insight...
I think the issue is simple to reproduce by having a property that is typed as a `Uri`. I've worked around it by temporarily using a `string` instead.