Project

General

Profile

Actions

Architecture #26416

closed

JVM platform limit requires splitting services in RudderConfig

Added by Clark ANDRIANASOLO 3 months ago. Updated 29 days ago.

Status:
Released
Priority:
N/A
Category:
Architecture - Code maintenance
Target version:
Effort required:
Small
Name check:
To do
Fix check:
To do
Regression:
No

Description

We have a compilation error platform restriction a parameter list's length cannot exceed 254 when adding new lazy val into RudderConfig initialization in rudder-web.
We would need to properly split the initialization module into submodules to prevent this every time we add new structures.

Actions #1

Updated by Vincent MEMBRÉ 2 months ago

  • Target version changed from 8.3.0~beta1 to 8.3.0~rc1
Actions #2

Updated by François ARMAND about 1 month ago

  • Target version changed from 8.3.0~rc1 to 8.2.6
Actions #3

Updated by François ARMAND about 1 month ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions #4

Updated by François ARMAND about 1 month ago

  • Target version changed from 8.2.6 to 8.3.0~rc1
Actions #5

Updated by François ARMAND about 1 month ago

So, targeting 8.3 in the end, because what seems to repair deals with API which changed a lot between Rudder 8.2 and 8.3, so it would lead to merge problem in any case.

Actions #6

Updated by François ARMAND about 1 month ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/6284
Actions #7

Updated by Anonymous about 1 month ago

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

Updated by Vincent MEMBRÉ 29 days ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 8.3.0~rc1 which was released today.

Actions

Also available in: Atom PDF