-
Notifications
You must be signed in to change notification settings - Fork 212
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
Comments
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 |
You're absolutely right! I confirmed locally. |
@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 |
I cannot re-test it, because I had to refresh the cache to confirm @Nemo157's point. But I'm ok with closing it :) . |
It's been 2 days since I made a release of
fs-tree
that introduced a method calledread_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

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

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 indeed0.5.5
.Problem is not found in local
rustdoc
pages.The text was updated successfully, but these errors were encountered: