Product CSV import error report file missing

[mischabraam]

Preconditions (*)

1. Magento 2.3.5-p1

Steps to reproduce (*)

1. Import a product CSV which will generate errors like a not existing path to an image.

Expected result (*)

1. An error_report.csv file with the errors generated in the import.

Actual result (*)

1. No file..... the file is generated, but will be removed after the application ends.

The following causes this problem, see my comment in the destructor.
bc06501?diff=split#r39524421

Additional information

• detailed steps during confirmation on 2.4-develop Product CSV import error report file missing #28420 (comment)
• Product CSV import error report file missing #28420 (comment)

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• 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”.

[m2-assistant]

Hi @mischabraam. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @swathishs. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[swathishs]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @swathishs. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @swathishs, here is your Magento instance.
Admin access: https://i-28420-2-4-develop.instances.magento-community.engineering/admin_70b5
Login: 014ba51e Password: ccb37a638d04
Instance will be terminated in up to 3 hours.

[swathishs]

@mischabraam: The issue is reproducible in Magento 2.4-develop instance

Please find the attachment below:

1.Check the data

2. After import

3. Click on error file

Viedo -

[mischabraam]

Yes, I saw the commit I mentioned is also in de 2.4-develop branch.