Skip to content
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

[release/6.0] Update zip extraction to never throw any exceptions when the LastWriteTime update fails #64192

Merged
merged 1 commit into from
Feb 7, 2022

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jan 24, 2022

Backport of #63912 to release/6.0

/cc @adamsitnik @EatonZ

Customer Impact

After successful extraction to a file, the file handle is closed. After that, it's opened again to set the last write time. As reported by customer in #63912 some AV software can open it in the meantime and lock the access to the file. As the end result, Windows customers, who have AV software installed can sporadically observe an IOException (ERROR_SHARING_VIOLATION).

Testing

I was not able to reproduce this bug locally and I don't think that it's possible to implement a reliable test for it.

Risk

Can't see any.

@ghost
Copy link

ghost commented Jan 24, 2022

Tagging subscribers to this area: @dotnet/area-system-io-compression
See info in area-owners.md if you want to be subscribed.

Issue Details

Backport of #63912 to release/6.0

/cc @adamsitnik @EatonZ

Customer Impact

Testing

Risk

Author: github-actions[bot]
Assignees: -
Labels:

area-System.IO.Compression

Milestone: -

@adamsitnik adamsitnik added the Servicing-consider Issue for next servicing release review label Jan 24, 2022
@leecow leecow added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Jan 25, 2022
@leecow leecow added this to the 6.0.3 milestone Jan 25, 2022
@EatonZ
Copy link
Contributor

EatonZ commented Jan 26, 2022

I appreciated the approval for a servicing release.👍
When do you think 6.0.3 will release?

@danmoseley
Copy link
Member

When do you think 6.0.3 will release?

Scheduled for 2nd week of March.

@safern
Copy link
Member

safern commented Feb 7, 2022

Failures are unrelated. System.Text.Json failure is: #61524

Diagnostics failure seems to be a machine in a bad state:

System.InvalidOperationException : Cannot load Counter Name data because an invalid index '' was read from the registry. Performance counters on the machine may need to be repaired.

@safern safern merged commit 3b0b34c into release/6.0 Feb 7, 2022
@safern safern deleted the backport/pr-63912-to-release/6.0 branch February 7, 2022 19:09
@ghost ghost locked as resolved and limited conversation to collaborators Mar 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants