kunwp1 opened a new pull request, #6313: URL: https://github.com/apache/texera/pull/6313
### What changes were proposed in this PR? Backport of #6306 to `release/v1.2` (cherry-pick of the four PR commits `3fd0068`, `b47c5a6`, `ade89a2`, `8e28e13`; one conflict in `frontend/src/jsdom-svg-polyfill.ts` — this branch carries an older revision of that file — resolved by re-adding the `ResizeObserver` stub in the branch's style). This fixes bulk uploads of many files to a dataset being extremely slow (~1,100 files took ~12 minutes) because the Pending and Finished lists fully re-rendered on every change-detection pass on the same thread driving the uploads. The backport carries the complete fix from #6306: a Map-backed pending queue with a memoized `queuedFileNames` snapshot, `cdk-virtual-scroll` + `trackBy` on the Pending and staged-changes lists, an `auditTime`-coalesced staged-objects refetch (at most one dataset-diff request per second instead of one per finished file) with optimistic Finished-count updates so both headers move in real time, viewport re-measure on collapse-panel expand, and two upload-slot-leak fixes (`totalTime === 0` finishes and same-name re-uploads within the 5s hide window). See #6306 for the review discussion and a screen recording of a 1,100-file upload. ### Any related issues, documentation, discussions? Backport of #6306, which fixes #5586 on `main` (as of this backport, #6306 is still awaiting merge). ### How was this PR tested? The two component spec files shipped with the fix were run on this branch (`ng test --include '**/user-dataset-explorer/dataset-detail.component.spec.ts' --include '**/user-dataset-staged-objects-list.component.spec.ts'`): 26/26 passed. `yarn format:ci` passes. On #6306, Codecov reports all modified lines covered. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code, Claude Fable 5 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
