-
Notifications
You must be signed in to change notification settings - Fork 861
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
feat: Add NewListDirectoryPathsPager for azuredatalake #23905
base: main
Are you sure you want to change the base?
feat: Add NewListDirectoryPathsPager for azuredatalake #23905
Conversation
Thank you for your contribution @paulbrittain! We will review the pull request and get back to you soon. |
@paulbrittain please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
/azp run go - azdatalake |
Azure Pipelines successfully started running 1 pipeline(s). |
I also ran the live test (unrecorded, which runs live on a storage account) pipeline, and it seems to fail for the new test added. Find the error below - |
I've added more tests to I took a closer look at the failure: The tests are adding a Test When a prefix of dir1 The expected results have been changed to expect this. Could you please run the azdatalake pipeline again? |
/azp run go - azdatalake |
Azure Pipelines successfully started running 1 pipeline(s). |
@paulbrittain , |
601a448
to
bc2318f
Compare
bc2318f
to
f8edeab
Compare
/azp run go - azdatalake |
Azure Pipelines successfully started running 1 pipeline(s). |
I tried to fix the pipeline by making changes to the changelog file, but I do not have access to push to your fork. Error in the test from backend - |
azure-sdk-for-go
issue: #23852other relevant issue: Azure/azure-rest-api-specs#31894
@tanyasethi-msft Please review 🙂