Project

General

Profile

Actions
Copy link

Bug #25617

open

Discordance on node compliance between two tabs

Added by Lucas FRANCOIS about 2 months ago. Updated about 4 hours ago.

Status:
New
Priority:
2
Assignee:
Vincent MEMBRÉ
Category:
Web - UI & UX
Target version:
8.1.9
Pull Request:
Severity:
Trivial - no functional impact | cosmetic
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description



When in nodes tab it shows 100% of compliance, but when clicking on the node it now shows 99%.

Files

Download all files
clipboard-202410071048-thrap.png (6.03 KB) clipboard-202410071048-thrap.png Lucas FRANCOIS, 2024-10-07 10:48
clipboard-202410071048-0uti6.png (39.9 KB) clipboard-202410071048-0uti6.png Lucas FRANCOIS, 2024-10-07 10:48
clipboard-202410101357-9jpqo.png (59.5 KB) clipboard-202410101357-9jpqo.png Nicolas CHARLES, 2024-10-10 13:57
Actions
Copy link
 #1

Updated by Lucas FRANCOIS about 1 month ago

  • Priority changed from N/A to To review
Actions
Copy link
 #2

Updated by François ARMAND about 1 month ago

  • Assignee set to Raphael GAUTHIER
  • Priority changed from To review to 2
Actions
Copy link
 #3

Updated by François ARMAND about 1 month ago

  • Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ

It seems that the compliance score is not using the specified algo to compute compliance, which leads to rounding errors.

Actions
Copy link
 #4

Updated by Nicolas CHARLES about 1 month ago

the compliance does not sum up to 100 on the nodes page

Actions
Copy link
 #5

Updated by Raphael GAUTHIER 28 days ago

  • Status changed from New to In progress
  • Assignee changed from Vincent MEMBRÉ to Raphael GAUTHIER
Actions
Copy link
 #6

Updated by Raphael GAUTHIER 28 days ago

  • Status changed from In progress to New
  • Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ 13 days ago

  • Target version changed from 8.1.8 to 8.1.9
Actions
Copy link
 #8

Updated by François ARMAND about 4 hours ago

On this one, we must understand why it was not caught by our unit tests and if it really use the algo that we have decided. @Vincent MEMBRÉ, can you:

- understand why we fall on that again,
- add the missing unit tests if some are missing (either in elm or scala),
- normalize the computation of percents so that we only have one way to do it (and same algo in scala, in elm)

Actions
Copy link

Also available in: Atom PDF