Conversation
fix(queue): disable SQL cache when reading queued items QueueItemRepository::findOldestQueuedItems() read the queue with executeS() and the default $use_cache = true. The query uses a nested subquery with an alias, which PrestaShop's cache invalidation does not always associate with the queue table, so the cached result was never purged when new tasks were enqueued. As a result the task runner read a stale queue snapshot from Memcached and did not see newly enqueued SendDraftTask items, so shipment drafts for new orders stayed pending until the queue was read fresh (e.g. from the module config page). Reading without cache makes the runner always see freshly enqueued tasks.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fix(queue): disable SQL cache when reading queued items
QueueItemRepository::findOldestQueuedItems() read the queue with executeS() and the default $use_cache = true. The query uses a nested subquery with an alias, which PrestaShop's cache invalidation does not always associate with the queue table, so the cached result was never purged when new tasks were enqueued.
As a result the task runner read a stale queue snapshot from Memcached and did not see newly enqueued SendDraftTask items, so shipment drafts for new orders stayed pending until the queue was read fresh (e.g. from the module config page).
Reading without cache makes the runner always see freshly enqueued tasks.