magento / magento/catalog-storefront
Sync with 2.4: Product Feed index process unknown error
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 7
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Need to fix error in integration test after sync with mainline
PR: https://github.com/magento/catalog-storefront/pull/403
Error: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/catalog-storefront/pull/403/a74a6c3a2764e6febfda634d93cfb7b0/Integration/allure-report-ee/index.html
Magento\Setup\Console\Command\GenerateFixturesCommandTest.testExecute
Design Config Grid index has been rebuilt successfully in 00:00:00
Customer Grid index has been rebuilt successfully in 00:00:00
Category Products index has been rebuilt successfully in 00:00:00
Product Categories index has been rebuilt successfully in 00:00:00
Catalog Rule Product index has been rebuilt successfully in 00:00:00
Product EAV index has been rebuilt successfully in 00:00:00
Product Price index has been rebuilt successfully in 00:00:00
Product Attributes Feed index has been rebuilt successfully in 00:00:00
Category Feed index has been rebuilt successfully in 00:00:00
Stock index has been rebuilt successfully in 00:00:00
Catalog Product Rule index has been rebuilt successfully in 00:00:00
Product Feed index process unknown error:
SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
Product/Target Rule index process unknown error:
SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
Target Rule/Product index process unknown error:
SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
Catalog Search index process unknown error:
SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
Sales Rule index process unknown error:
SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Magento\Setup\Console\Command\GenerateFixturesCommandTest.testExecute and the linked integration-test report for PR #403. Reproduce the Product Feed indexing failure, trace the MySQL server-gone-away error, and confirm that the fixture generation test completes without the unknown index-process errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql, php
- Domain
- databases, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100