-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[Bug]: in RC1 copy is failing to overwrite on Linux in some cases that previously succeeded #9250
Comments
This allows an opt-in workaround for dotnet#9250 that affected deployment processes can use, mitigating the risk of entirely reverting dotnet#8685.
For 8.0.100-RC2, we added an explicit control to opt back into the old behavior Long term I like this proposal from @danmoseley
|
Well, I liked it. But in fact that's what we're already doing Lines 288 to 291 in 3847162
Where msbuild/src/Shared/FileUtilities.cs Lines 857 to 866 in 3847162
and msbuild/src/Shared/ExceptionHandling.cs Lines 147 to 162 in 3847162
So unless there's some other exception being fired here (when I try to overwrite a running app on Windows I get |
the ticket is blocked by the undergoing release process in the App Services team. |
The package with patched msbuild was given to app services. We are waiting for extended logs results. |
@YuliiaKovalova Please update status of this issue. |
App Service team hasn't gathered logs yet. |
We have agreed to close it since the requested info wasn't provided and there is a doable way to workaround the issue. |
Issue Description
This was on an internal Mariner deployment. The message is access denied eg
began in 7.0.400 and
MSBUILDDISABLEFEATURESFROMVERSION=17.8
is confirmed to make it go away.Below is @rainersigwald theory
We don't know why the overwrite was working but the delete isn't, and can get traces.
We need to get some fix into RC2. Perhaps reverting the copy task at least for Linux?
Steps to Reproduce
.
Expected Behavior
.
Actual Behavior
.
Analysis
No response
Versions & Configurations
No response
The text was updated successfully, but these errors were encountered: