[COMPASS-6598] Deleting multiple aggregation stages quickly creates ghost stage frame Created: 13/Mar/23  Updated: 10/Jan/24  Resolved: 11/Jul/23

Status: Closed
Project: Compass
Component/s: Aggregation pipeline
Affects Version/s: 1.35.0
Fix Version/s: No version

Type: Bug Priority: Minor - P4
Reporter: Rhys Howell Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS:
node.js / npm versions:
Additional info:


Attachments: File Screen Recording 2023-03-13 at 14.13.32.mov    
Documentation Changes: Not Needed
Sprint: Up for triaging

 Description   

Screen Recording 2023-03-13 at 14.13.32.mov

Looks like when multiple stages are removed quickly, an empty stage that cannot be interacted with can exist in the pipeline.

This is a bit harder to do now than before as the remove stage button is now in a menu, however it still should be able to happen.

My hunch as to what's happening is a race condition with loading the preview. We probably want to ignore preview results when the underlying pipeline has changed and they are no longer relevant.

Reported on slack:
https://mongodb.slack.com/archives/C0U7K0MC3/p1678713461139429 



 Comments   
Comment by Rhys Howell [ 11/Jul/23 ]

Still exists, unless we change the ux folks shouldn't be able to reproduce this.

Generated at Wed Feb 07 22:43:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.