fix(volume-group): always keep accessibility consistent with all volumes in group #1284
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #1284 +/- ##
=======================================
Coverage 36.65% 36.65%
=======================================
Files 28 28
Lines 2218 2218
=======================================
Hits 813 813
Misses 1302 1302
Partials 103 103 ☔ View full report in Codecov by Sentry. |
…nsistent with all volumes Signed-off-by: SSmallMonster <mingming.zhou@daocloud.io>
SSmallMonster
force-pushed
the
fix-lvg
branch
from
f51709c
to
6728d38
Compare
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 this PR does / why we need it:
part of fix of #1276
Special notes for your reviewer:
Does this PR introduce a user-facing change?