[MGNLUI-6871] Grid row not updating reliably after change in underlying datasource Created: 09/Sep/21  Updated: 11/Oct/21  Resolved: 17/Sep/21

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

Type: Bug Priority: Neutral
Reporter: Michael Duerig Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File AssetsCoreFunctionalTests_addFolderToRoot.flv.mp4     File AssetsCoreFunctionalTests_addSubFolders.flv.mp4     File AssetsCoreFunctionalTests_duplicateAsset.flv.mp4     File AssetsCoreFunctionalTests_renameAsset.flv.mp4     PNG File image-2021-09-09-13-53-36-616.png    
Issue Links:
Problem/Incident
causes MGNLTEST-165 contentApp.hasRow("yet-another-page")... Closed
causes MGNLUI-6912 Observation in JCR browser broken aft... Closed
is caused by MGNLUI-6736 Frozen admincentral after restart (af... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Epic Link: Grid performance

 Description   

Steps to reproduce

  1.  Run one of AssetsCoreFunctionalTests#addFolderToRoot, AssetsCoreFunctionalTests#duplicateAsset,
    AssetsCoreFunctionalTests#addSubFolders, AssetsCoreFunctionalTests#renameAsset on Jenkins until the test fails
  2.  Watch the video to see that the status bar does reflect the change in the item but the grid does not update.

Expected results

None of above tests should fail.

Actual results

These tests fail once in a while (1 out of ten times or so).

Workaround

Refresh the page or switch the grid view.

Development notes

This seems like a regression from MGNLUI-6736. It looks like those changes can cause ui pushes to get skipped. Simulating this in the debugger and skipping the 2nd ui.push in JcrDataSourceObservation after changing a grid item results in the behaviour observed.

Since some of the videos show a loading bar and some don't, there seem to be two different but related problems. The stuck loading bar should have been fixed with MGNLUI-6736.



 Comments   
Comment by Roman Kovařík [ 13/Sep/21 ]

For the record, MGNLUI-6736 was reverted on a feature branch, but the issue remained.

Generated at Mon Feb 12 09:40:50 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.