Baselines create a multiple definition error
Priority
Description
Related
Activity
Show:

Mileva BriandJune 13, 2024 at 9:39 AM
Flag added
Waiting for Customer feedback

Mileva BriandOctober 6, 2023 at 2:13 PM
Might be related to but not a 100% sure

Mileva BriandOctober 5, 2023 at 8:47 AMEdited
Both tickets 2726 and 2696 associated are duplicates from the same team
Flagged
Resolved
Details
Details
Assignee
Reporter

Sprint
Time tracking
3d 7h logged1h remaining
Components
Release date
Jan 07, 2025
Requirement Yogi
Linked requirements
Requirement Yogi
Linked requirements
Created September 7, 2023 at 10:24 AM
Updated January 7, 2025 at 4:34 PM
Resolved October 24, 2023 at 8:24 AM
Implementation
In 3.6.6, we’ve removed some features of our caches, which were too complex to be accurately maintained. We didn’t lose much performance, because it is now a background job.
In 3.6.7, we’ve added an upgrade task to cleanup the inconsistent records.
We are still waiting for informations from customers to better diagnose the issue.
Explanation
With the version 1 engine, it may happen that we create baselines from cached pages, this might be what is causing the issue. The user cannot go to version 2 because there are different features and they won’t be able to compare baselines.
Original description
The users are creating baselines from the page and when doing so, they receive an “error: NullPointerException: null. The baseline is an error and should be deleted.” All requirements of the page are highlighted in red and appear as there is a multiple definition. When clicking on the second original page, it goes to a previous version in the page.
App version : 3.6.1
Indexing engine: Version 1
Confluence Version: 7.19.8