-
Notifications
You must be signed in to change notification settings - Fork 2.1k
adding enableSmbDirectoryLease property #46362
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
adding enableSmbDirectoryLease property #46362
Conversation
API Change CheckAPIView identified API level changes in this PR and created the following API reviews |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this looks good! please look into my comments before you merge, but if they do not apply you can ignore them.
String testShareName = generateShareName(); | ||
ShareServiceClient serviceClient = primaryFileServiceClient; | ||
ShareClient shareClient = serviceClient.getShareClient(testShareName); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
don't we new up a primaryShareClient
in the setup
method? can we use that instead of creating a new shareClient every time? my question applies to the other tests too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this will be addressed before stg100 is merged in
} finally { | ||
shareClient.delete(); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why are we deleting the share here? does the automatic test cleanup not detect this share? same with the other tests as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The explicit shareClient.delete(); in the finally block ensures that the test-created share is always deleted, even if an assertion fails or an exception is thrown.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The explicit shareClient.delete(); in the finally block ensures that the test-created share is always deleted, even if an assertion fails or an exception is thrown.
if the assertion fails or an exception is thrown, the test cleanup method kicks in and the share will be deleted. the only time this doesn't apply is if we use a special account, like a premium account. so we should remove these deletes before we merge the 100 branch into main
12ccb88
into
feature/storage/stg100base
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines