Search index not updated after renaming/moving of a page

[dojutsu-user]

#5845 renames APIv3 Design Document from Design of APIv3 to APIv3 Design Document but the search results still contains both results.

Related link: https://docs.readthedocs.io/en/latest/index.html?rtd_search=apiv3

[stsewd]

There is this error on sentry, maybe related to this issue

update or delete on table "projects_importedfile" violates foreign key constraint "sphinx_domains_sphin_html_file_id_a0307e9f_fk_projects_" on table "sphinx_domains_sphinxdomain"

It happens here

readthedocs.org/readthedocs/projects/tasks.py

Lines 1640 to 1647 in e53af66

	# Delete ImportedFiles objects (including HTMLFiles)
	# from the previous build of the version.
	(
	ImportedFile.objects
	.filter(project=version.project, version=version)
	.exclude(build=build)
	.delete()
	)

https://sentry.io/organizations/read-the-docs/issues/1144425753/?project=148442&query=is%3Aunresolved&statsPeriod=14d

[hiddeco]

Not sure if this is related, but for https://docs.fluxcd.io, we also notice that renamed files and files removed from git aren't removed from the index.

E.g. first result for this search: https://docs.fluxcd.io/en/latest/search.html?q=ignore&check_keywords=yes&area=default

[dojutsu-user]

@hiddeco
I think wiping the version and then rebuilding the docs should fix the problem.
You can find the steps for it here: https://docs.readthedocs.io/en/stable/guides/wipe-environment.html

[hiddeco]

@dojutsu-user already did this before I commented, without any effect.

[jcampbell]

Thanks @stsewd for flagging this still-open issue. We're observing this on the great expectations docs (https://great-expectations.readthedocs.io/en/latest/). Searching for a moved page shows both the new (working) and broken link. I have tried wiping and rebuilding to no effect.

[Flid]

Also affecting https://kedro.readthedocs.io, most of the search queries show the broken links first, since we've moved some stuff around.

[Flid]

@dojutsu-user Can you please confirm if the bug is actually fixed for you?
Nothing changed for our project.

[humitos]

It's fixed but it's not deployed yet.

[madelyngreyes]

Do we have a status on the deployment of the possible fix by chance?

[stsewd]

@madelyngreyes it's already deployed. If you still have this problem, you should try rebuilding the version.

[Flid]

Our issue has been fixed after the release. Thank you!

[madelyngreyes]

The issue was fixed on our end as well, thank you!