Magento2: Product images are being duplicated on import

[simonworkhouse]

When importing product data the product images are being duplicated for each import run.

Preconditions

1. Magento 2.4-develop
2. PHP 7.3
3. MySQL 5.7.25

Steps to reproduce

1. composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition <install dir>
2. cd <install dir>
3. ./bin/magento setup:install --backend-frontname=? --db-host=? --db-name=? --db-user=? --db-password=? --base-url=? --admin-user=? --admin-password=? --admin-email=? --admin-firstname=? --admin-lastname=?
4. mkdir var/import-images
5. Add images test-1.jpg, test-2.jpg, test-3.jpg and test-4.jpg inside the path <install dir>/var/import-images. Any valid jpeg will do.
6. Import the product CSV data below _twice_

"sku","product_online","website_id","store_view_code","attribute_set_code","product_type","categories","name","description","short_description","visibility","price","special_price","special_price_from_date","special_price_to_date","url_key","meta_title","meta_keywords","meta_description","display_product_options_in","msrp_display_actual_price_type","additional_attributes","qty","out_of_stock_qty","use_config_min_qty","is_qty_decimal","allow_backorders","use_config_backorders","min_cart_qty","use_config_min_sale_qty","max_cart_qty","use_config_max_sale_qty","is_in_stock","use_config_notify_stock_qty","manage_stock","use_config_manage_stock","use_config_qty_increments","qty_increments","use_config_enable_qty_inc","enable_qty_increments","is_decimal_divided","deferred_stock_update","use_config_deferred_stock_update","related_skus","crosssell_skus","upsell_skus","custom_options","bundle_price_type","bundle_sku_type","bundle_price_view","bundle_weight_type","bundle_values","associated_skus","base_image","base_image_label","small_image","small_image_label","thumbnail_image","thumbnail_image_label","swatch_image","swatch_image_label","additional_images","additional_image_labels","configurable_variations"
"some-test-product",1,1,,"Default","simple","Default Category/Some Category/Some Test Product","Some test product","This is just some test product",,"Catalog, Search",2999,,,,"some-test-product","Some test product",,,"Block after Info Column","Use config",,100,0,1,0,0,1,1,0,0,1,1,1,0,1,1,0,1,0,0,0,1,,,,,,,,,,,"test-1.jpg",,"test-1.jpg",,"test-1.jpg",,"test-1.jpg",,"test-3.jpg",,
"another-test-product",1,1,,"Default","simple","Default Category/Some Category/Some Test Product","Some test product","This is just some test product",,"Catalog, Search",2999,,,,"another-test-product","Another test product",,,"Block after Info Column","Use config",,100,0,1,0,0,1,1,0,0,1,1,1,0,1,1,0,1,0,0,0,1,,,,,,,,,,,"test-2.jpg",,"test-2.jpg",,"test-2.jpg",,"test-2.jpg",,"test-4.jpg",,

Import settings

• Entity Type: Products
• Import Behavior: Add/Update
• Stop on Error (default)
• Allowed Errors Count: 10 (default)
• Field separator: , (default)
• Multiple value separator: , (default)
• Empty attribute value constant: __EMPTY__VALUE__ (default)
• Fields Enclosure: Not checked (default)
• Images File Directory: var/import/images/import-images

Expected result

Products end up with each product image only attached once.

Actual result

Products end up with all product images duplicated.

[magento-engcom-team]

Hi @simonworkhouse. 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-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

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

@simonworkhouse do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• [ ] yes
• [ ] no

[magento-engcom-team]

Hi @engcom-backlog-nazar. 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: :point_down:

• [ ] 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.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• _Next steps are available in case you are a member of Community Maintainers._

• [ ] 6. Add label Issue: Confirmed once verification is complete.

• [ ] 7. Make sure that automatic system confirms that report has been added to the backlog.

[dipti2jcommerce]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

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

[magento-engcom-team]

Hi @dipti2jcommerce, here is your Magento instance.
Admin access: https://i-21885-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[magento-engcom-team]

:white_check_mark: Confirmed by @engcom-backlog-nazar
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-98840 were created

Issue Available: @engcom-backlog-nazar, _You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself._

[tnsezer]

I would like to share some point about the issue. It happens in Magento\CatalogImportExport\Model\Import\Product.php line 1772. If add a variable for exists images in mapper like _media_is_disabled, it should be fix it but the code try to match it with path. That why it doesn't work.

[dmanners]

Thank you for the information @tnsezer

[erfanimani]

Duplicate of #14398

See PR here: https://github.com/magento/magento2/pull/21146

[erfanimani]

Actually, there's a better PR here, based on mine but it also deals with image deletion: https://github.com/magento/magento2/pull/21855

[dmanners]

@erfanimani thanks for the update. Are the issues duplicated or the PRs?

[erfanimani]

@dmanners Both actually — this issue is a duplicate of #14398

But then there are two open PRs (I referenced them both in case someone wants to create a patch for it):

• #21855
• #21146

[soundararajanm1990]

I am working on this at #dmcdindia1

[magento-engcom-team]

@soundararajanm1990 thank you for joining. Please accept team invitation here and self-assign the issue.

[m2-assistant[bot]]

Hi @soundararajanm1990. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• [ ] 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

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

• [ ] 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• [ ] 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[yogeshkhasturi]

Hi @soundararajanm1990,

Have you fixed this issue? its also coming when trying to Duplicate product.

Thanks
Yogesh

[duckchip]

what's the status on this issue?

[soundararajanm1990]

We can't solve this issue. Still now pending.

[Beagon]

We are encountering this too and since the import is ran daily this really clutters up the media gallery. Is there any workaround anyone can recommend?

[kevinvuillemin]

I have same problem, magento2.3.2 duplicated images after import product csv.

Did you find a solution ?

[erfanimani]

Two workarounds exist, scroll up to see the relevant pull requests/commits. You'll need a developer to create and apply Composer patches for your Magento version. Seems Magento is too busy to review/merge and fix the bug themselves though..

[Beagon]

@erfanimani Yes, we indeed used a combination of the solutions (with some minor edits). Really odd that Magento doesn't look at the fixes because the importer is a vital part of most webshops.

[kevinvuillemin]

Thank you @erfanimani

With a combination of the solutions, the import works very well.

[MackieeE]

+1 Hoping to see this merged in soon, big help this :)

[skapin]

Wow same trouble for us... This is awsome magento let this kind of BUG in a 2.3.2 version released worldwild...

[skapin]

@kevinvuillemin can you share the working solution ? I'm strugeling with all the PR closed and open speaking around it. Thank you in advance

[kevinvuillemin]

@skapin, of course ! how do you want me to share the file?

[skapin]

@kevinvuillemin you can send me a mail to skapinthefourb gmailcom address for example, or create a repository

As you want. Thank you so much :)

[kevinvuillemin]

@skapin that's good for you ?

https://gist.github.com/kevinvuillemin/802cc5e4b476e73c1c5838b143bd6a51

[skapin]

@kevinvuillemin It works on the first try. Copy/paste instead of Product.php and _voila_ !
Magento version : 2.3.2

[kevinvuillemin]

Et voila !
Au plaisir ;-)

[soundararajanm1990]

@kevinvuillemin Your code not working in Magento version : 2.3.1

[kevinvuillemin]

Working with 2.3.2 for me, are you sure ?

[soundararajanm1990]

yes we used 2.3.1 not working

[skapin]

@soundararajanm1990 I think they have changed the Product.php class for the release of Magento 2.3.2.

The easier is to upgrade (maintenance & safety)

[MackieeE]

@kevinvuillemin They moved the issue #14398 onto a new phase - does this mean your PR is ready for Testing on the next Dev version?

[ahmadwaliesipick]

any update on this issue?

[Yonn-Trimoreau]

Below is a more permanent solution.

Be careful, this will trash previous duplicates if there were any.

Make a preference on Magento\CatalogImportExport\Model\Import\Product and copy/paste this code in it:

```
use const DIRECTORY_SEPARATOR;

class Product extends Magento\CatalogImportExport\Model\Import\Product
{
private $bunch;
private $imagesToRemove;

protected function getExistingImages($bunch)
{
    $this->bunch = $bunch;

    return parent::getExistingImages($bunch);
}

public function addImageHashes(&$imagesBySku)
{
    parent::addImageHashes($imagesBySku);

    // get existing images (from db)
    $existingImages = [];
    foreach ($imagesBySku as $sku => $images) {
        foreach ($images as $path => $imageInfo) {
            if (!isset($existingImages[$imageInfo['hash']])) {
                $existingImages[$imageInfo['hash']] = [];
            }

            $existingImages[$imageInfo['hash']][] = [
                'value_id' => $imageInfo['value_id'],
                'path' => $path
            ];
        }
    }

    // get imported images (from file)
    $importDir = $this->_mediaDirectory->getAbsolutePath($this->getImportDir());

    $importedImages = [];
    foreach ($this->bunch as $rowData) {
        foreach ($this->getImagesFromRow($rowData)[0] as $imagesFromRow) {
            $imageNames = explode($this->getMultipleValueSeparator(), $imagesFromRow[0]);

            $imageHashes = array_flip(array_map(function($imageName) use ($importDir) {
                $filename = $importDir . DIRECTORY_SEPARATOR . $imageName;

                return $this->_mediaDirectory->isReadable($filename) ? md5_file($filename) : '';
            }, $imageNames));

            $importedImages = array_merge($importedImages, $imageHashes);
        }
    }

    // guess images to remove
    $this->imagesToRemove = array_diff_key($existingImages, $importedImages);
}

protected function _saveMediaGallery(array $mediaGalleryData)
{
    // remove duplicate images
    $valueIds = [];
    if (!empty($this->imagesToRemove)) {
        // from disk
        foreach ($this->imagesToRemove as $imagesToRemove) {
            foreach ($imagesToRemove as $imageToRemove) {
                $imagePath = 'pub/media/catalog/product' . $imageToRemove['path'];

                if ($this->_mediaDirectory->isExist($imagePath)) {
                    $this->_mediaDirectory->delete($imagePath);
                }

                $valueIds[] = $imageToRemove['value_id'];
            }
        }

        // from database
        $this->getConnection()->delete(
            $this->getConnection()->getTableName('catalog_product_entity_media_gallery'),
            $this->getConnection()->quoteInto('value_id IN (?)', $valueIds)
        );
    }

    return parent::_saveMediaGallery($mediaGalleryData);
}

}

[MackieeE]

Well sadly this looks like it missed the 2.3.3 ship :(

[kevinvuillemin]

Realy ? That’s not cool.

But This fix working ? :

https://gist.github.com/kevinvuillemin/802cc5e4b476e73c1c5838b143bd6a51

[simonworkhouse]

Normally I would be surprised that it has been so long without a resolution, but I have come to expect this from Magento. Anyway, I have had to resolve this issue for a project recently and it appears that the offending commit was https://github.com/magento/magento2/commit/7803eed11f8bf490bf8905ab0577091c7e782156

I worked around this by adding a preference for a class that extends Magento\CatalogImportExport\Model\Import\Product and just overrides the uploadMediaFiles(...) function to force the $renameFileOff variable to be true.

This addresses the issue in our specific use case, but it does not address the underlying issues with the way that images are managed in Magento. Additionally, it will also undo whatever "fix" that commit was attempting to do.

[jg-development]

@simonworkhouse
Can you please share the code with me?

[jalung]

Product-revised-version.txt

version 2.3.3
Atttached is the patch that is used to fix the issue in our use case. Magento import is expecting images to have the dynamic paths it created on export. However, the CSV is hand crafted and the image names are plain; "blablabla.jpg" as opposed to "/b/l/a/blablabla_60.jpg". This patch works repeatedly because the CSV file is from the same feed. The patch basically strips off the "/b/l/a/" and "_60" and makes a match to the existing image(s) for that product.

[duckchip]

Does anyone have a fix for 2.3.3 with an including fix to remove duplicates? Our server just exploded to 55gb on images because of the duplication during the import..

[duckchip]

the commit that @simonworkhouse referred to, was the suicide bomber in our case as well.
Patching that to the previous implementation fixed it.
In my opinion this really should be reverted.

[SlowFamily]

@jalung 's patch worked for me, except for that Magento 2.3.3 (if not earlier versions) renames images all lowercase, so the image name preg_match needs to be case insensitive. Patch with that change here: Product-revised-version.txt

[jalung]

Product-revised-version.txt
Fixed case where CSV row has new and existing images.

[guido7171]

Also missed the 2.3.4 ship. @jalung 's patch is working fine for me in 2.3.4. Still needs more testing, for my case, where images are updated by sku, but have same name.jpg.

[hostep]

Possible fix in https://github.com/magento/magento2/pull/26713

[hostep]

I've seen some change in the codebase of Magento 2.3.5 which might fix this issue. Would be great if somebody could verify this after 2.3.5 is officially released on 28 April.

[erfanimani]

Thank @hostep , let's hope that's the case! I should be able to verify soon after the release.

[jg-development]

@erfanimani
OK, I can confirm that the images are now no more duplicated on import.
That is very good...
BUT.....
The Add/Update does not delete images either.
Example:
I import a product (sample_1) with 8 images => fine
Add/Import the product sample_1 with 2 images .... the product is not correctly updated, still 8 images in the db.

[Yonn-Trimoreau]

@jg-development, if you're importing your images from disk, my fix should work. If you're using urls, don't bother trying my fix.

[jg-development]

@Yonn-Trimoreau
I am importing from disk.
Should your fix including the deleting of existing images?

[Yonn-Trimoreau]

Yes

[jg-development]

hmmm did not work for me.

sku,store_view_code,attribute_set_code,product_type,categories,product_websites,name,description,short_description,weight,product_online,tax_class_name,visibility,price,special_price,special_price_from_date,special_price_to_date,url_key,meta_title,meta_keywords,meta_description,base_image,base_image_label,small_image,small_image_label,thumbnail_image,thumbnail_image_label,created_at,updated_at,new_from_date,new_to_date,display_product_options_in,map_price,msrp_price,map_enabled,gift_message_available,custom_design,custom_design_from,custom_design_to,custom_layout_update,page_layout,product_options_container,msrp_display_actual_price_type,country_of_manufacture,additional_attributes,qty,out_of_stock_qty,use_config_min_qty,is_qty_decimal,allow_backorders,use_config_backorders,min_cart_qty,use_config_min_sale_qty,max_cart_qty,use_config_max_sale_qty,is_in_stock,notify_on_stock_below,use_config_notify_stock_qtymanage_stock,use_config_manage_stock,use_config_qty_increments,qty_increments,use_config_enable_qty_inc,enable_qty_increments,is_decimal_divided,website_id,related_skus,related_position,crosssell_skus,crosssell_position,upsell_skus,upsell_position,additional_images,additional_image_labels,custom_options,_super_products_sku,_super_attribute_code,_super_attribute_option,_associated_sku,_associated_default_qty,_associated_position
P06342,,Default,simple,Default Category/Blumen/Rosenknospe,base,P06342,,,,1,,"Catalog, Search",1.05,,,,,,,,P06342-oR-Alt-Copper.jpg,,P06342-oR-Alt-Gold.jpg,,P06342-oR-Alt-Messing.jpg,,,,,,,,,,,,,,,,,,,"usage=Anhänger,further_processing=,length=30.1,width=46.4,height=7,rings=6,stone_nr=,stone_size=,material=To,material_form=blech,material_width=52,material_strength=0.6,net_weight=4960,gross_weight=10220,presses=Yes,presses_tool=Yes,presses_machine=360,first_breakout=,first_breakout_tool=,first_breakout_machine=,second_breakout=,second_breakout_tool=,second_breakout_machine=,third_breakout=,third_breakout_tool=,third_breakout_machine=,repressing=,repressing_tool=,repressing_machine=,punching=Yes,punching_tool=Yes,punching_machine=5TO,punching_strips=Yes,punching_strips_size=,punching_strips_tool=Yes,punching_strips_machine=5TO,punching_single=,punching_single_size=,punching_single_tool=,punching_single_machine=,emboss=,emboss_tool=,emboss_machine=,dished=,dished_tool=,dished_machine=,bombe=,bombe_tool=,bombe_machine=,wave=,wave_tool=,wave_machine=,centre_hole=,centre_hole_tool=,centre_hole_machine=,polishing=,degreasing=,annealing=,scouring=Yes,notes=durchbrechen 5+1 Ringe / 1 Ring oben / 5 Ringe unten",1,0.0000,1,,,1,,1,,1,1,,1,1,1,,1,,,0,,,,,,,"/P06342-oR-Alt-Gold.jpg,/P06342-oR-Alt-Messing.jpg,/P06342-oR-Alt-Silver.jpg,/P06342-oR-Glanz-Gold.jpg,/P06342-oR-Glanz-Gun Metal.jpg,/P06342-oR-Glanz-Platin.jpg,/P06342-oR-Glanz-Raw.jpg,/P06342-oR-Glanz-Rose Gold.jpg,/P06342-oR-Glanz-Silver.jpg",,,,,,,,

This is my first import.
Second was only with 2 additional images.

[erfanimani]

Hi, @hostep this issue still exists in Magento 2.3.5-p1 — I was able to replicate it.

edit: all that those changed did was break all the PRs and patches ;)

edit2: I'm using this PR with success now: https://github.com/magento/magento2/pull/26713

[gigulinu]

2.3.5-p1 duplicate images - issue not fixed

[chandu-pinpoint]

@magento I'm working on this

[PsmIndia]

2.3.4 duplicate images - issue not fixed

[jalung]

It does not work for most of us because we have in our import CSV the base name of the image, for example;
base_image_78989.jpg but magento's existing images are named /b/a/base_image_78989_10.jpg. Unless there is a comparison between these two names on updating the product, this issue will persist.

[guido7171]

@PsmIndia @jalung
Check PR https://github.com/magento/magento2/pull/26713
The PR comes with image hash compare logic, which is working fine (in my workflow) for the community version.

[HenKun]

I can confirm #26713 is working fine on 2.3.5-p1. Since this seems to be an endless issue, here the link to the correct application of this patch via composer: https://devdocs.magento.com/guides/v2.4/comp-mgr/patching.html

[HenKun]

I noticed that the PR has another issue: If you import data for another store (e.g. english translations) without any image related data in the import CSV, all images get removed (globally). Images should only be removed if the according image columns are present and empty.

[goutam1github]

How can I get this patch. Anyone please advise.

[Yonn-Trimoreau]

Get the patch corresponding to the pull request : https://patch-diff.githubusercontent.com/raw/magento/magento2/pull/26713.patch
And apply it to magento/catalog-import-export composer dependency using https://github.com/cweagans/composer-patches

[goutam1github]

Hello,
I was trying to install the patch but getting errors. Magento unable to apply this patch.

Any one please advise. Attaching the screenshot.

[HenKun]

Hello,
I was trying to install the patch but getting errors. Magento unable to apply this patch.

Any one please advise. Attaching the screenshot.

See https://github.com/magento/magento2/issues/21885#issuecomment-644777537 for detailed instructions how to apply the patch

[Yonn-Trimoreau]

Try removing the PATCH [2/4] part entirely, and the last part about tests.

[goutam1github]

Hi Yonn,

Its a very long file. Could you please help me telling which line to which line.
Thanks.

[oviliz]

So sad to see @magento-admin ignoring this...

[cannycookie]

We also need this resolving, was hopeful 2.4 would have brought some fresh updates but at present we have to drop all images before importing otherwise end up with new images duplicated, empty and set as base, small and thumb :-(

[riconeitzel]

Can anyone confirm this happens with API imports as well? We upgraded from 2.3.3 to 2.3.5 and noticed various images being duplicated. It seems that's related to the number oft store views. basically for every store view a new copy.

[KBUnulleins]

Temporary solution to this issue:

1. Edit this file:
/vendor/magento/module-catalog-import-export/Model/Import/Uploader.php:134

2. Modify init() function:
Change line 134 in the init() function from

$this->setAllowRenameFiles(true);

to

$this->setAllowRenameFiles(false);

Result:
This will replace the product images instead of just renaming and duplicating them.

Keep in mind:
This is just a temporary solution and with the next magento-update you have to do this again.
To make the changes permanent you have to create a module that overrides this file.

This is my first comment on github. So please be kind with your feedback - thanks!

---

For the Magento dev team:

• Would be great if you could set the default behavior through the magento backend.
• Would be awesome to do a filesize comparison in /vendor/magento/module-catalog-import-export/Model/Import/Uploader.php getNewFileName() and just renameing it if the filesize has changed.

[magento-engcom-team]

:white_check_mark: Confirmed by @engcom-Alfa
Thank you for verifying the issue. Based on the provided information internal tickets MC-38267 were created

Issue Available: @engcom-Alfa, _You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself._

[magento-engcom-team]

Hi @simonworkhouse. Thank you for your report.
The issue has been fixed in magento/magento2#26713 by @PieterCappelle in 2.4-develop branch
Related commit(s):

• 912b3f7737259d5977ce3fa64781a3280c712bfe
• ffdb34112974d74aa2d72b5fd441641e85234ad3
• eb8607c5ab62f10e519e20810da60a2755c34d58
• e4812b842f300af4f45dd9d6ed3a6faaa2143a38
• d03b223d33cc511b482f83c2666469c2e9c19e3f
• d4931f79648bfd1677a861257697d5f8a57cecd6
• f16a12f6bad4a60c50223ab6aab7bc924fc5e437
• 819fc7cfef122559826edbfd17ce397527461ae1
• f16811c29421f34c9ae1b07d080b7ec0107c9757
• bca6bf6db9f3eeca2f10c753c34a23b568307bdf
• 3da6f23f4fb20553580431bdcdbb35afb4551d7f
• 9b505ee45d9d40dd9b030f8ef88e64204a1b56d4

The fix will be available with the upcoming 2.4.2 release.