-
Notifications
You must be signed in to change notification settings - Fork 1
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
Fsck display tree #92
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: yichen88 <[email protected]>
Signed-off-by: yichen88 <[email protected]>
Signed-off-by: yichen88 <[email protected]>
Signed-off-by: yichen88 <[email protected]>
nodes.get(rowBean.id).children.add(rowBean.cId); | ||
} | ||
if (row.getUUID(4) == null) { | ||
root.children.add(rowBean.id); |
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.
Looks like the tree is displayed multiple times because we don't check here if the node has already been added:
if the root node of the filesystem has multiple children, it will appear multiple times in the table (once for itself, once for each children), so we will go through that code multiple times
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.
Looks like the tree is displayed multiple times because we don't check here if the node has already been added:
if the root node of the filesystem has multiple children, it will appear multiple times in the table (once for itself, once for each children), so we will go through that code multiple times
Fixed by 'Set'
Signed-off-by: yichen88 <[email protected]>
SonarCloud Quality Gate failed. |
Please check if the PR fulfills these requirements (please use
'[x]'
to check the checkboxes, or submit the PR and then click the checkboxes)Does this PR already have an issue describing the problem ? If so, link to this issue using
'#XXX'
and skip the restWhat kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change or deprecate an API? If yes, check the following:
Other information:
(if any of the questions/checkboxes don't apply, please delete them entirely)