[Bug] The version shown in the list of packages is older then the latest versions displayed inside the package page

[unkarjedy]

Current behavior

I've just uploaded the latest version of sbt-idea-plugin
https://github.com/JetBrains/sbt-idea-plugin

The latest version is now 4.0.3
You can see it in the official source of truth:
https://central.sonatype.com/artifact/org.jetbrains/sbt-idea-plugin_2.12_1.0

When I open
https://index.scala-lang.org/jetbrains
I see the older version 4.0.2 in the list:

However, if I click on it, I can see the latest version 4.0.3

Expected Behavior

I expect the version in the list of packages to display the latest version.

Extra comments

No response

Search terms

No response

[adpi2]

Thanks for the report

[adpi2]

The issue resolved itself automatically.

The search base is synced asynchronously by a background job, and it can take up to 30 min. This explains the temporary inconsistency, though in this case, it appears to have persisted much longer. I am not sure why, as there is nothing suspicious in the logs.

[unkarjedy]

It's understandable that there is some delay.
However, there seems to be inconsistency in how the versions are retrieved on two pages.
When you open the project, you can see the latest version in the list.

Is it fetched on-demand from repo when viewing the list?
Or is the version there because sync already happened?

In the first case, if the requests were made via a single point in the code, this info could be used to update the cached latest version.

[adpi2]

At the moment the search page is only powered by the search engine whereas the project page is only powered by the database, hence the inconsistency.

The database is our source of truth. So after we get the search response, and before rendering the page, we could use it to get the up-to-date view of each project. If so, we should do the same for the awesome page.

[adpi2]

In the first case, if the requests were made via a single point in the code, this info could be used to update the cached latest version.

That's another possibility, we could update the search view, each time we load a project page.

[unkarjedy]

So after we get the search response, and before rendering the page, we could use it to get the up-to-date view of each project. If so, we should do the same for the awesome page.

I actually meant something like this