Skip to content

Conversation

@serprex
Copy link
Contributor

@serprex serprex commented Feb 7, 2022

#16295 was not fixed by #16354 because all options must be repeated in following requests, not just marker. ie prefix would be dropped when paging

This PR opts to modify the passed in options. It's probably preferable to clone the options to a variable within scope to avoid mutating caller's options

@ghost ghost added Storage Storage Service (Queues, Blobs, Files) customer-reported Issues that are reported by GitHub users external to the Azure organization. labels Feb 7, 2022
@ghost
Copy link

ghost commented Feb 7, 2022

Thank you for your contribution serprex! We will review the pull request and get back to you soon.

@serprex
Copy link
Contributor Author

serprex commented Feb 7, 2022

@adreed-msft @mohsha-msft

@check-enforcer
Copy link

check-enforcer bot commented Feb 7, 2022

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them. In order to bootstrap pipelines for a new service, please perform following steps:

For track 2 SDKs Issue the following command as a pull request comment:

/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run go - [service] - ci

serprex pushed a commit to citusdata/wal-g that referenced this pull request Feb 8, 2022
Fork has fix for ListBlobsHierarchy: Azure/azure-sdk-for-go#16992

This bug causes wal-g to sometimes claim backup-list is empty, or truncated,
causing restoring LATEST to either fail or begin with a very old backup
serprex pushed a commit to citusdata/wal-g that referenced this pull request Feb 8, 2022
Specific commit used because I'm not sure when a new version will be made,
but there's a particularly important fix:
Azure/azure-sdk-for-go#16354 fixes ListBlobsHierarchy when paging is necessary
which turns out to be a broken fix, so a fork is used in the meantime which includes a proper fix:
Azure/azure-sdk-for-go#16992

On some containers paging happens much sooner than MaxResults would imply,
causing restoring LATEST to either fail because wal-g can't find backups, or wal-g selects an old backup

There are two other notable PRs:
Azure/azure-sdk-for-go#16067 fixes a chunk pooling bug
Azure/azure-sdk-for-go#15958 removes the need for FakeIoReadCloser
serprex pushed a commit to wal-g/wal-g that referenced this pull request Feb 8, 2022
Specific commit used because I'm not sure when a new version will be made,
but there's a particularly important fix:
Azure/azure-sdk-for-go#16354 fixes ListBlobsHierarchy when paging is necessary
which turns out to be a broken fix, so a fork is used in the meantime which includes a proper fix:
Azure/azure-sdk-for-go#16992

On some containers paging happens much sooner than MaxResults would imply,
causing restoring LATEST to either fail because wal-g can't find backups, or wal-g selects an old backup

There are two other notable PRs:
Azure/azure-sdk-for-go#16067 fixes a chunk pooling bug
Azure/azure-sdk-for-go#15958 removes the need for FakeIoReadCloser
serprex pushed a commit to wal-g/wal-g that referenced this pull request Feb 8, 2022
Specific commit used because I'm not sure when a new version will be made,
but there's a particularly important fix:
Azure/azure-sdk-for-go#16354 fixes ListBlobsHierarchy when paging is necessary
which turns out to be a broken fix, so a fork is used in the meantime which includes a proper fix:
Azure/azure-sdk-for-go#16992

On some containers paging happens much sooner than MaxResults would imply,
causing restoring LATEST to either fail because wal-g can't find backups, or wal-g selects an old backup

There are two other notable PRs:
Azure/azure-sdk-for-go#16067 fixes a chunk pooling bug
Azure/azure-sdk-for-go#15958 removes the need for FakeIoReadCloser
@mohsha-msft mohsha-msft changed the base branch from main to mohsha-msft/fix-listing-metadata-parsing February 8, 2022 15:28
@mohsha-msft mohsha-msft merged commit 6ef7037 into Azure:mohsha-msft/fix-listing-metadata-parsing Feb 8, 2022
@mohsha-msft
Copy link
Contributor

Thanks for your contribution @serprex . I've merged it with the next release candidate.

mohsha-msft added a commit that referenced this pull request Feb 9, 2022
* Manual fixes in generated models to adapt azcore 0.21

* Fix SAS Creation + other issue (#16901)

* Fix SAS Creation + other issue

* Added README.md + Fix comment

* Removed Specification File.

* Updated CHANGELOG

* Regenerated Recordings + Ran Live Tests (#16990)

* [Storage] convert options to take pointer (#16978)

* convert to nil

* changelog entry

* adding a comment about nil, changing o to options for better clarity

* Bumped up AzCore to the latest version

* azblob: fix ListBlob to preserve prefix while paging (#16992)

* [Storage] improving documentation (#16945)

* improving documentation

* updating changelog

* ctx -> context.TODO(), simplifying comments

* updating a few more examples

* improving docs further

* Update sdk/storage/azblob/zt_examples_test.go

Co-authored-by: Kim Ying <[email protected]>

* Update sdk/storage/azblob/zt_examples_test.go

Co-authored-by: Kim Ying <[email protected]>

* Update sdk/storage/azblob/zt_examples_test.go

Co-authored-by: Kim Ying <[email protected]>

* Update sdk/storage/azblob/zt_examples_test.go

Co-authored-by: Kim Ying <[email protected]>

* Update sdk/storage/azblob/zt_examples_test.go

Co-authored-by: Kim Ying <[email protected]>

* finished doc updates

* Background -> TODO

* valid container name

* updating readme

* Update sdk/storage/azblob/README.md

Co-authored-by: Kim Ying <[email protected]>

* Update sdk/storage/azblob/README.md

Co-authored-by: Kim Ying <[email protected]>

* removing todos

* more comments and additions

* set env vars with bash

* Azure Storage Blob -> Azure Blob Storage

* Update CHANGELOG.md

* forcing a change

Co-authored-by: Kim Ying <[email protected]>

* Added Release Date in CHANGELOG.

Co-authored-by: Sean Kane <[email protected]>
Co-authored-by: Philip Dubé <[email protected]>
Co-authored-by: Kim Ying <[email protected]>
serprex pushed a commit to wal-g/wal-g that referenced this pull request Feb 14, 2022
Specific commit used because I'm not sure when a new version will be made,
but there's a particularly important fix:
Azure/azure-sdk-for-go#16354 fixes ListBlobsHierarchy when paging is necessary
which turns out to be a broken fix, so a fork is used in the meantime which includes a proper fix:
Azure/azure-sdk-for-go#16992

On some containers paging happens much sooner than MaxResults would imply,
causing restoring LATEST to either fail because wal-g can't find backups, or wal-g selects an old backup

There are two other notable PRs:
Azure/azure-sdk-for-go#16067 fixes a chunk pooling bug
Azure/azure-sdk-for-go#15958 removes the need for FakeIoReadCloser
serprex pushed a commit to wal-g/wal-g that referenced this pull request Feb 14, 2022
Specific commit used because I'm not sure when a new version will be made,
but there's a particularly important fix:
Azure/azure-sdk-for-go#16354 fixes ListBlobsHierarchy when paging is necessary
which turns out to be a broken fix, so a fork is used in the meantime which includes a proper fix:
Azure/azure-sdk-for-go#16992

On some containers paging happens much sooner than MaxResults would imply,
causing restoring LATEST to either fail because wal-g can't find backups, or wal-g selects an old backup

There are two other notable PRs:
Azure/azure-sdk-for-go#16067 fixes a chunk pooling bug
Azure/azure-sdk-for-go#15958 removes the need for FakeIoReadCloser
serprex pushed a commit to wal-g/wal-g that referenced this pull request Feb 14, 2022
Specific commit used because I'm not sure when a new version will be made,
but there's a particularly important fix:
Azure/azure-sdk-for-go#16354 fixes ListBlobsHierarchy when paging is necessary
which turns out to be a broken fix, so a fork is used in the meantime which includes a proper fix:
Azure/azure-sdk-for-go#16992

On some containers paging happens much sooner than MaxResults would imply,
causing restoring LATEST to either fail because wal-g can't find backups, or wal-g selects an old backup

There are two other notable PRs:
Azure/azure-sdk-for-go#16067 fixes a chunk pooling bug
Azure/azure-sdk-for-go#15958 removes the need for FakeIoReadCloser
serprex pushed a commit to wal-g/wal-g that referenced this pull request Feb 15, 2022
Specific commit used because I'm not sure when a new version will be made,
but there's a particularly important fix:
Azure/azure-sdk-for-go#16354 fixes ListBlobsHierarchy when paging is necessary
which turns out to be a broken fix, so a fork is used in the meantime which includes a proper fix:
Azure/azure-sdk-for-go#16992

On some containers paging happens much sooner than MaxResults would imply,
causing restoring LATEST to either fail because wal-g can't find backups, or wal-g selects an old backup

There are two other notable PRs:
Azure/azure-sdk-for-go#16067 fixes a chunk pooling bug
Azure/azure-sdk-for-go#15958 removes the need for FakeIoReadCloser
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

customer-reported Issues that are reported by GitHub users external to the Azure organization. Storage Storage Service (Queues, Blobs, Files)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants