You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After running vip @example.env -- wp vip-search index --indexables="term" --version="next" the document_count for Version 2 of the Index should be accurate via vip @example.env -- wp vip-search index-versions list term.
Actual Behavior
After running vip @example.env -- wp vip-search index --indexables="term" --version="next" the document_count for Version 2 of the Index is intermittently 0 via vip @example.env -- wp vip-search index-versions list term. First 0, then 253681, then 0, then 253681 and staying consistent after some time.
As an aside, vip @example.env -- wp vip-search health validate-terms-count was always accurate. Still, the buggy document_count introduces confusion and doubt.
Note: vip -v = 3.7.0
Steps to Reproduce the Problem
vip @example.env -- wp vip-search index --indexables="term" --version="next"
vip @example.env -- wp vip-search index-versions list term (was 0)
vip @example.env -- wp vip-search index-versions list term (was 253681)
vip @example.env -- wp vip-search health validate-terms-count (no problem)
vip @example.env -- wp vip-search index-versions list term (was 0)
vip @example.env -- wp vip-search index-versions list term (was 253681)
The text was updated successfully, but these errors were encountered:
NinjutsuSunrise
changed the title
vip @example-env -- wp vip-search index-versions list term returns document_count = 0 intermittently for fresh Version 2vip @example.env -- wp vip-search index-versions list term returns document_count = 0 intermittently for fresh Version 2
Jul 25, 2024
This issue has been marked stale because it has been open for 60 days with no activity. If there is no activity within 7 days, it will be closed.
This is an automation to keep issues manageable and actionable and is not a comment on the quality of this issue nor on the work done so far. Closed issues are still valuable to the project and are available to be searched.
Expected/Desired Behavior
After running
vip @example.env -- wp vip-search index --indexables="term" --version="next"
the document_count for Version 2 of the Index should be accurate viavip @example.env -- wp vip-search index-versions list term
.Actual Behavior
After running
vip @example.env -- wp vip-search index --indexables="term" --version="next"
the document_count for Version 2 of the Index is intermittently 0 viavip @example.env -- wp vip-search index-versions list term
. First 0, then 253681, then 0, then 253681 and staying consistent after some time.As an aside,
vip @example.env -- wp vip-search health validate-terms-count
was always accurate. Still, the buggy document_count introduces confusion and doubt.Note:
vip -v
= 3.7.0Steps to Reproduce the Problem
vip @example.env -- wp vip-search index --indexables="term" --version="next"
vip @example.env -- wp vip-search index-versions list term
(was 0)vip @example.env -- wp vip-search index-versions list term
(was 253681)vip @example.env -- wp vip-search health validate-terms-count
(no problem)vip @example.env -- wp vip-search index-versions list term
(was 0)vip @example.env -- wp vip-search index-versions list term
(was 253681)The text was updated successfully, but these errors were encountered: