Plugin search no longer matches by plugin name

[yani.iliev]

Plugin search on WordPress.org appears to be broken. Searching by plugin name no longer returns the expected plugin as the top result. Instead, results seem to be limited to matching against plugin descriptions only.

Steps to reproduce:

1. Go to the WordPress.org plugin directory search (or use the in-admin plugin search)
2. Search for akismet
3. Observe that results return plugins that mention "akismet" in their description, rather than the Akismet plugin itself

Expected behavior:
Searching for a plugin by its exact name should return that plugin as the first result.

Actual behavior:
The plugin name field appears to no longer be included in the search index/ranking. Results only reflect description-level matches.

Confirmed by: Multiple users in WordPress.org Slack (#meta channel) -- wojsmol, macmanx.

[dd32]

This has been resolved, again. As such I'm going to mark this ticket as resolved.

The underlying cause appears to likely be a race condition in the Jetpack sync / Elastic Search indexing process. This hasn't been fully confirmed, but is actively being investigated by the team.

I'm going to commit some new tooling for plugin reviewers/admins such that plugin reviewers can see/validate the state of the index, this isn't a fix for this, but rather a way to see if it's a problem (Both that the issue is resolved, and confirm if it's happened again).

[dd32]

In 14765:

Plugin Directory: Admin: Add ElasticSearch index metabox and status tool.

Adds a new metabox on plugin admin edit screens showing current ES status, to allow plugin reviewers to confirm that a plugin is indeed in the search index.

Adds a new plugin admin tool to allow bulk-query of the ES index to verify the contents is correct (Note: It should be, this is just to validate that).

Adds an ability to reindex plugins, by touching metadata / firing Jetpack sync actions, in the rare event it becomes out of sync.
This would likely only occur due to downtime on WordPress.org/WordPress.com, or when we cause Jetpack sync to not work.

See #8210

[yani.iliev]

Really appreciate how quickly you jumped on this @dd32. I reported it, I went for a nap and when I woke up it is already resolved. Great work, thank you.