ajansveld
ajansveld
Why is this considered an "enhancement"? We just had our first incident because of this destructive bug, I feel we should be much louder about this. Is this being looked...
What is the threshold for backporting the fix to 7.2 (LTS-current), considering it is supported for another 2 years?
This was supposedly fixed in Microsoft.Data.SqlClient v4.0.1 (and System.Data.SqlClient v4.8.4). Are there any plans to update to that (or the latest) version?
@doctorpangloss I noticed the same, were you able to patch the files in this directory? Seems like it might be harder than just running the patcher as System.
Is this on the roadmap for 7.3?
This was fixed in https://github.com/PowerShell/PowerShell/pull/18735 (as stated in https://github.com/PowerShell/PowerShell/issues/18850, which is a duplicate of this issue). This issue can be closed.
Already a fan of vscode but this would really take it to the next level.
It works if you update the uri to this: ```Register-PSResourceRepository -Name ProGet -Uri https://$ServerDomain/nuget/$FeedName/v3/index.json -Trusted``` This is documented here: https://docs.inedo.com/docs/proget-feeds-nuget#using-the-nuget-api
> @ajansveld I just tried to repro this on a connector based feed in ProGet _(that proxies PSGallery)_ but any `Find-PSResource`/`Install-PSResource` return 404 when hitting ProGet's v3 URL. > >...
@Jaykul do you believe this is still an issue? I cannot repro the problem (as long as the correct uri is used).