Actions
Bug #16537
closedNode never updated because of nonEmpty in place of isEmpty
Status:
Released
Priority:
N/A
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
During upmerge of parent task, a nonEmpty replaced a isEmpty leading to never actually updating nodes.
Updated by François ARMAND almost 5 years ago
- Status changed from New to In progress
Updated by François ARMAND almost 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/2713
Updated by François ARMAND almost 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|7b912750d6da066d2ecc487bbaae6bff5f9243cc.
Updated by François ARMAND almost 5 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ almost 5 years ago
- Related to Bug #16524: we should not use .size to check if a collection is empty added
Updated by Vincent MEMBRÉ over 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.3 which was released today.
Actions