[MAGNOLIA-9242] Revert locking of the config workspace Created: 09/Jan/24  Updated: 30/Jan/24  Resolved: 30/Jan/24

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3.0

Type: Task Priority: Neutral
Reporter: Mikaël Geljić Assignee: Antonín Juran
Resolution: Fixed Votes: 0
Labels: dx-core-6.3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Release notes required:
Yes
Documentation update required:
Yes
Epic Link: 6.3 Consolidation
T-Shirt Size: Small
Work Started:

 Description   

not relevant in DX Core

check commits introducing and modifying RepositoryManager#doInUnlockedConfigWorkspace, mostly from CLOUD-105 (one mis-tagged as CLOUD-1005), CLOUD-888 and a misqualified QA commit too. Those I could find so far, via git log -S doInUnlockedConfigWorkspace or similar:

  • c30935ce493 QA Let the consumers of the RepositoryManager.doInUnlockedConfigWorkspace choose their own config session
  • 476c9e9321e CLOUD-1005 Temporarily unlock the config workspace in order to store the pairing keys
  • b5ec0fbf58b CLOUD-105 Only lock the config workspace when a specific flag is set
  • 8fec6c9eff6 CLOUD-105 Protect the config workspace from writing by locking the root node

There may be a few more or conflicts.


Generated at Mon Feb 12 04:39:54 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.