Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Azure Storage STG105 Feature Tests

オープン
#7,449 コメント 0 件 リアクション 0 件 担当者 1 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@Jinming-Hu がすでに取り組んでいます。

2026年10月6日 から。

評価

この issue はまだ評価されていません。

説明

Client Storage

Track follow-up work for the STG105 test coverage in #7448. The following tests currently run only in PLAYBACK. Revisit them when the features are enabled on the normal production/CI test accounts, with the goal of running in both LIVE and PLAYBACK.

Session authentication: production enablement

Requires session creation to be enabled on the normal Blob and DataLake test accounts.

  • SessionAuthenticationRecordedTest.DownloadsWithDefaultSessionProvider_PLAYBACKONLY_
  • SessionAuthenticationRecordedTest.IndependentClientsShareExplicitSessionProvider_PLAYBACKONLY_
  • DataLakeSessionAuthenticationRecordedTest.DownloadUsesSessionAuthentication_PLAYBACKONLY_

Data locality: production enablement and prepared test data

Requires layout/download-hint support and a prepared 64 MiB blob/file. The multi-endpoint cases also require a layout spanning multiple endpoints. The DataLake cases currently unconditionally skip outside PLAYBACK and reuse Blob recordings; adapt that setup to support LIVE execution.

  • DataLocalityRecordedTest.GetLayoutMultipleEndpoints_PLAYBACKONLY_
  • DataLocalityRecordedTest.GetLayoutRangeReturnsFullBlobSize_PLAYBACKONLY_
  • DataLakeLocalityRecordedTest.GetLayoutAndDownloadHint_PLAYBACKONLY_
  • DataLakeLocalityRecordedTest.GetLayoutRangeReturnsFullFileSize_PLAYBACKONLY_

Azure Files: share creation-time production enablement

Requires freshly created shares to expose x-ms-share-creation-time in Get Share Properties and <Creation-Time> in List Shares responses on the normal CI accounts. Older preexisting shares may legitimately omit creation time.

  • FileShareClientTest.ShareProperties_PLAYBACKONLY_
  • FileShareServiceClientTest.ListShares_PLAYBACKONLY_

The complete existing ShareProperties and ListShares cases are temporarily playback-only, including their quota and general listing coverage. Restore the full cases to LIVE when creation-time support is available; keep the creation-time assertions intact.

Azure Files: Change Feed production enablement

Requires share Change Feed creation/configuration to be supported and Get Share Properties to return its enabled flag, retention period, and managed change-feed container.

  • FileShareClientTest.ChangeFeed_PLAYBACKONLY_

Azure Files: file-ID addressing production enablement

Requires addressing files and directories by file ID, including file-ID Get Properties and Get File Links, to be supported on the normal CI accounts.

  • FileShareFileClientTest.FileIdAddressing_PLAYBACKONLY_

For each case above: establish the prerequisites, remove the _PLAYBACKONLY_ restriction, regenerate recordings under the new names, update any recording-name references, and confirm both LIVE and PLAYBACK execution.

NFS: special setup, not just production rollout

  • NfsFileShareClientTest.ListAllNfsEntryTypes_PLAYBACKONLY_

This case requires directories, regular files, symlinks, block devices, character devices, FIFOs, and sockets. The fixture currently creates an empty NFS share. Keep this case playback-only until an NFS-mounted setup can provision and clean up all required entry types; production feature enablement alone is insufficient.

主要言語
C++
スター
206
フォーク
177
平均マージ
2日 17時間
マージ済み PR(30日)
37

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Azure/azure-sdk-for-cpp のほかの issue

Azure/azure-sdk-for-cpp の issue をすべて見る

似ている issue

C++ の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。