From 9c3c2f2f12b333057a94d491f61a60e57985e1ab Mon Sep 17 00:00:00 2001 From: Jeanmarcos Juarez Date: Mon, 3 Aug 2026 16:59:16 -0400 Subject: [PATCH] docs(inventory-stock-visualizer): note the performance-toolkit fixture generator conflict --- InventoryStockVisualizer/README.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/InventoryStockVisualizer/README.md b/InventoryStockVisualizer/README.md index 2e4de8e5e59..7898b9ea85a 100644 --- a/InventoryStockVisualizer/README.md +++ b/InventoryStockVisualizer/README.md @@ -152,6 +152,29 @@ without a manual cache flush. `bin/magento queue:consumers:start inventory.stockvisualizer.purge` (or via the standard consumer cron). +### Generating performance-toolkit fixtures + +While this module is enabled, `setup:performance:generate-fixtures` aborts with +`The entity ID field for the "queue_message" table wasn't found`. + +The fixture generator saves one template product and uses `SqlCollector` to record +every `INSERT INTO` that save emits, treating each captured table as belonging to the +product entity. Saving the template writes source items, which fires the supply seam +and publishes a purge message onto the database-backed queue, so `queue_message` ends +up in that set. `EntityGenerator` then looks for a foreign key from it to +`catalog_product_entity`, finds none, and throws. + +Disable the module while generating the catalog: + + bin/magento module:disable Magento_InventoryStockVisualizer + bin/magento setup:performance:generate-fixtures + bin/magento module:enable Magento_InventoryStockVisualizer + bin/magento setup:di:compile + +This affects fixture generation only — never storefront or admin behaviour. Any module +that publishes to the database-backed queue during a product save runs into the same +generator limitation. + ## Extension points and service contracts Public service contracts live in this module's `Api` namespace: