[GCP FileShare Support] Fix for Invalid memory address or nil pointer dereference for GCP Fileshare Creation #1105
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nto Resolve-Issues
Codecov Report
@@ Coverage Diff @@
## master #1105 +/- ##
==========================================
- Coverage 48.09% 48.03% -0.07%
==========================================
Files 10 10
Lines 1420 1422 +2
==========================================
Hits 683 683
- Misses 687 689 +2
Partials 50 50
|
kumarashit
reviewed
Sep 27, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it: This PR will fix for nil pointer derefence for FileShare resouces in the service layer
Which issue(s) this PR fixes:
Fixes #1104
Test Report Added?:
Test Report:
Special notes for your reviewer: