Project

General

Profile

Actions

Bug #14770

closed

Invalid comparision of String and Option[String] in HistorizationService

Added by Nicolas CHARLES almost 5 years ago. Updated almost 5 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Maintenance
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

Compiling Rudder in 4.1 causes

[WARNING] /home/nicolas/dev/4.3/rudder/webapp/sources/rudder/rudder-core/src/main/scala/com/normation/rudder/services/eventlog/HistorizationService.scala:120: warning: Option[String] and String are unrelated: they will most likely always compare unequal
[WARNING]         case Some(entry) => (entry.nodeName != x.hostname || entry.nodeDescription != x.description )
[WARNING]                                                                                    ^
[WARNING] /home/nicolas/dev/4.3/rudder/webapp/sources/rudder/rudder-core/src/main/scala/com/normation/rudder/services/eventlog/HistorizationService.scala:146: warning: Option[String] and String are unrelated: they will most likely always compare unequal
[WARNING]            entry.groupDescription != x.nodeGroup.description ||
[WARNING]                                   ^
[WARNING] /home/nicolas/dev/4.3/rudder/webapp/sources/rudder/rudder-core/src/main/scala/com/normation/rudder/services/eventlog/HistorizationService.scala:181: warning: Option[String] and String are unrelated: they will most likely always compare unequal
[WARNING]            || entry.directiveDescription != directive.shortDescription
[WARNING]                                          ^
[WARNING] /home/nicolas/dev/4.3/rudder/webapp/sources/rudder/rudder-core/src/main/scala/com/normation/rudder/services/eventlog/HistorizationService.scala:185: warning: Option[String] and String are unrelated: they will most likely always compare unequal
[WARNING]            || entry.techniqueDescription != technique.description


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #17778: table nodes contains on entry per node per generation, which is too muchReleasedFrançois ARMANDActions
Actions #1

Updated by Nicolas CHARLES almost 5 years ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
Actions #2

Updated by Nicolas CHARLES almost 5 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/2203
Actions #3

Updated by Rudder Quality Assistant almost 5 years ago

  • Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES
Actions #4

Updated by Nicolas CHARLES almost 5 years ago

  • Status changed from Pending technical review to Pending release
Actions #5

Updated by Vincent MEMBRÉ almost 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.1.22, 4.3.12 and 5.0.10 which were released today.

Actions #6

Updated by Nicolas CHARLES almost 4 years ago

  • Related to Bug #17778: table nodes contains on entry per node per generation, which is too much added
Actions

Also available in: Atom PDF