-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Open
Labels
Area: Import / exportComponent: ImportExportIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedPriority: P3May be fixed according to the position in the backlog.May be fixed according to the position in the backlog.Progress: ready for devReported on 2.4.xIndicates original Magento version for the Issue report.Indicates original Magento version for the Issue report.Reproduced on 2.4.xThe issue has been reproduced on latest 2.4-develop branchThe issue has been reproduced on latest 2.4-develop branch
Description
Preconditions and environment
- Magento version: 2.2.10, 2.3.5-p1, 2.4.4
(but very likely occurring on all versions of 2.2, 2.3 & 2.4) - Magento 2.4-develop
- PHP 8.1
- Magento instance with two Admin users
- Login with 2 different Machines
Steps to reproduce
- Create 2 admin users (A & B)
- Log in to the 2 admin users on 2 machines respectively
- Prepare 2 CSV files for product import (with different numbers of rows and contents)
(for example A.csv with 100 rows, B.csv with 50 rows) - Admin A uploads A.csv while admin B uploads B.csv at roughly the same time
Expected result
It is expected that both A & B could complete the import successfully and a total of 150 products would be imported.
Actual result
It turned out that the 2 import actions were somehow affecting each other.
If A clicked the Check Data
button slightly ahead of B, we would see the following message on BOTH screens.
(be reminded that the file A uploaded had 100 rows in it)
And this happened vice versa if B acted first.
And if at this moment A clicked the Import
button slightly ahead of B again, only the 50 rows in B.csv would be imported to the system.
Here is a list of logs we got after a few attempts (sometimes A acted first, sometimes B acted first).
It seems like the latter would always "overwrite" the previous one.
Additional information
No response
Release note
No response
Triage and priority
- Severity: S0 - Affects critical data or functionality and leaves users without workaround.
- Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
- Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
- Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
- Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
Metadata
Metadata
Assignees
Labels
Area: Import / exportComponent: ImportExportIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedPriority: P3May be fixed according to the position in the backlog.May be fixed according to the position in the backlog.Progress: ready for devReported on 2.4.xIndicates original Magento version for the Issue report.Indicates original Magento version for the Issue report.Reproduced on 2.4.xThe issue has been reproduced on latest 2.4-develop branchThe issue has been reproduced on latest 2.4-develop branch