Skip to content

Search box broken due to outdated cache not being updated #2243

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
marcospb19 opened this issue Oct 4, 2023 · 4 comments
Closed

Search box broken due to outdated cache not being updated #2243

marcospb19 opened this issue Oct 4, 2023 · 4 comments

Comments

@marcospb19
Copy link

marcospb19 commented Oct 4, 2023

It's been 2 days since I made a release of fs-tree that introduced a method called read_at.

However, when I go to the /latest/ documentation page, and search it, I get nothing:

https://docs.rs/fs-tree/latest/fs_tree/?search=fstree%3A%3Aread_at
image

In contrast, the /0.5.5/ page search bar works as expected:

https://docs.rs/fs-tree/0.5.5/fs_tree/index.html?search=read_at
image


This is specifically a problem with the search bar, since the method page can be seen in both versions:

https://docs.rs/fs-tree/latest/fs_tree/enum.FsTree.html#method.read_at
https://docs.rs/fs-tree/0.5.5/fs_tree/enum.FsTree.html#method.read_at


To be clear, the latest page shows that the version is indeed 0.5.5.

image


Problem is not found in local rustdoc pages.

@Nemo157
Copy link
Member

Nemo157 commented Oct 4, 2023

It works for me which makes it likely to be a local caching issue. I think it might be because 0.5.4 and 0.5.5 were built with the same rustdoc version, and that's the only part of the search-index-....js filename that varies between builds.

@marcospb19
Copy link
Author

marcospb19 commented Oct 4, 2023

You're absolutely right! I confirmed locally.

@marcospb19 marcospb19 changed the title Latest page search bar is broken Search box broken due to outdated cache not being updated Oct 4, 2023
@syphar
Copy link
Member

syphar commented Oct 5, 2023

@Nemo157 IMO this is the last remaining case of #1593 , and only can happen when two releases are build with the same nightly version.

I created an CDN invalidation for the crate.

If the search is fine now for @marcospb19 I would close this issue in favor of #1593

@marcospb19
Copy link
Author

I cannot re-test it, because I had to refresh the cache to confirm @Nemo157's point.

But I'm ok with closing it :) .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants