Skip to content

rustdoc: Enabling mergeable CCI broke the search functionality for the stdlib and for our internal docs #162334

Closed

Description

@fmease

Over at https://doc.rust-lang.org/nightly/nightly-rustc, it's impossible to find rustc_ast::ast::Attribute directly via the search feature.

Attribute

It doesn't matter if I search rustc_ast::ast::Attribute, rustc_ast::Attribute, ast::Attribute or Attribute.

Image

ast::Attribute & rustc_ast::Attribute & rustc_ast::ast::Attribute

Here, it "at least" indirectly lists the correct type as part of an associated function.

Image

Activity

  1. added
    T-rustdocRelevant to the rustdoc team, which will review and decide on the PR/issue.
    C-bugCategory: This is a bug.
    on Sep 5, 2026
  2. added
    needs-triageThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triaging
    T-rustdoc-frontendRelevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output.
    on Sep 5, 2026
  3. added
    E-needs-mcveCall for participation: This issue has a repro, but needs a Minimal Complete and Verifiable Example
    and removed
    needs-triageThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triaging
    on Sep 5, 2026
  4. fmease commented on Sep 5, 2026

    @fmease
    MemberAuthor

    This feels like a regression.

    I don't know if it's a rustdoc regression, a bootstrap regression or if it's only exhibited now because we've changed the compiler crates in some way like adding some public re-exports of rustc_ast::ast or rustc_ast::ast::Attribute to some other compiler crate (CC #145870 which is only tangentially related).

  5. theemathas commented on Sep 5, 2026

    @theemathas
    Contributor

    This also affects searching of the standard library (as of 0ed41eb41 2026-09-04). Searching for "PathBuf" doesn't find the PathBuf type. https://doc.rust-lang.org/nightly/std/index.html?search=PathBuf

    Image
  6. added
    I-prioritizeIssue needs a team member to assess the impact. Will be replaced by P-{low,medium,high,critical}
    on Sep 5, 2026
  7. added
    E-needs-bisectionCall for participation: This issue needs bisection: https://github.com/rust-lang/cargo-bisect-rustc
    on Sep 5, 2026
  8. fmease commented on Sep 5, 2026

    @fmease
    MemberAuthor

    Most likely due to #161716? That PR got merged 2 days ago, so part of nightly-2026-09-03 (rustc version) aka nightly-2026-09-04 (toolchain name) and it's very plausible that it messed with the search indices.

    cc @notriddle

  9. added
    S-has-bisectionStatus: A bisection has been found for this issue
    and removed
    E-needs-bisectionCall for participation: This issue needs bisection: https://github.com/rust-lang/cargo-bisect-rustc
    on Sep 5, 2026
  10. 3 remaining items

  11. removed
    I-prioritizeIssue needs a team member to assess the impact. Will be replaced by P-{low,medium,high,critical}
    on Sep 5, 2026
  12. added this to the 1.100.0 milestone on Sep 5, 2026
  13. jieyouxu commented on Sep 5, 2026

    @jieyouxu
    Member

    I'll try this locally with a revert 🤔 If it's due to #161716 I'd like to revert / reland that, it's not trivial certainly.

  14. jieyouxu commented on Sep 5, 2026

    @jieyouxu
    Member

    I looked at the rustc-docs locally too when reviewing the PR but also did not notice the difference 😓

  15. jieyouxu commented on Sep 5, 2026

    @jieyouxu
    Member

    Posted a revert: #162339

  16. notriddle commented on Sep 5, 2026

    @notriddle
    Contributor

    And a fix #162346

    Do we still want to land the revert?

  17. Zalathar commented on Sep 6, 2026

    @Zalathar
    Member

    Given that the fix-forward is in rustdoc rather than bootstrap, I’m inclined to follow the usual default practice of rolling back to a known-OK state and then working forwards from there, to avoid the risk of having an even bigger mess to revert.

  18. notriddle commented on Sep 6, 2026

    @notriddle
    Contributor

    Okay, let's do that. The fix-forward shouldn't conflict with the revert, anyway.

  19. added a commit that references this issue on Sep 6, 2026
  20. added a commit that references this issue on Sep 6, 2026
  21. added 3 commits that reference this issue on Sep 10, 2026
  22. added a commit that references this issue on Sep 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-rustdoc-searchArea: Rustdoc's search featureC-bugCategory: This is a bug.E-needs-mcveCall for participation: This issue has a repro, but needs a Minimal Complete and Verifiable ExampleP-criticalCritical priorityS-has-bisectionStatus: A bisection has been found for this issueT-rustdocRelevant to the rustdoc team, which will review and decide on the PR/issue.T-rustdoc-frontendRelevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output.regression-from-stable-to-nightlyPerformance or correctness regression from stable to nightly.

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions