Skip to content

Fix Azure object ETag consistency - #124

Merged
KSemenenko merged 1 commit into
mainfrom
codex/azure-object-etag-format
Oct 5, 2026
Merged

KSemenenko merged 1 commit into
mainfrom
codex/azure-object-etag-format

Conversation

@KSemenenko

Copy link
Copy Markdown
Member

Azure Blob listings and properties reads returned the same revision in different ETag formats, so a cleanup preview rejected an unchanged object as modified. Normalize returned ETags with the Azure SDK header format, preserving conditional stale-revision rejection. Bump the canonical package version to 10.0.17.

Validation:

  • The real Azurite regression reproduced the mismatch before the fix; the Azure object suite passes 7/7 after it.
  • Full non-stress test/coverage lane: 566 passed, 3 existing skips.
  • dotnet format ManagedCode.Storage.slnx and the final solution build pass with zero warnings/errors.
  • Coverage exception: measured aggregate coverage is 57.55% (prior full run 57.58%). This correction adds no production branches; the real Azure suite exercises the changed revision paths. The existing repository-wide coverage gap remains outside this provider repair.

Publication and consuming Prostir cleanup regression remain pending the protected main merge and canonical release. No local package or consumer workaround is used.

@KSemenenko
KSemenenko merged commit 38dbd8e into main Oct 5, 2026
4 checks passed
@KSemenenko
KSemenenko deleted the codex/azure-object-etag-format branch October 5, 2026 06:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant