Crate version exists on crates.io but is missing on docs.rs (not imported / not queued / not failed)

[mr-chelyshkin]

The crate taskvisor version 0.0.11 was successfully published to crates.io more than 8 hours ago,
but this version never appeared on docs.rs.

It is:

• Not listed on the crate page on docs.rs
• Not present in the build history
• Not present in the build queue
• Not marked as failed

0.0.11 returns “The requested version does not exist”.

This indicates that docs.rs never imported this version from the crates.io index.
The previous version 0.0.10 is present and documented normally.

What was expected

Docs.rs should import taskvisor 0.0.11 from the crates.io index and queue it for documentation build.

What happened instead

The version is completely absent on docs.rs, without any build attempt, queue entry, or error record.

--

Crate details

Description	Value
Crate name	taskvisor
Published version	0.0.11
crates.io page	https://crates.io/crates/taskvisor
docs.rs crate page	https://docs.rs/taskvisor (latest shown: 0.0.10)
Missing version URL	https://docs.rs/crate/taskvisor/0.0.11 “The requested version does not exist”
yanked	false

--

Local documentation build

The crate builds successfully with docs.rs-style rustdoc flags.
This is reproducible using the Taskfile.yml target:

task cargo/docs

cargo/docs:
  desc: Run 'rustdoc'.
  silent: true
  cmds:
    - task: _cargo/tool
      vars:
        CMD: >-
          +nightly rustdoc --lib -Zrustdoc-map --features "logging controller"
          -Zunstable-options -Zrustdoc-scrape-examples
          --config 'build.rustdocflags=["--cfg","docsrs","-Z","unstable-options","--cap-lints","warn"]'

--

Index

The version is present in the crates.io index:

git clone --depth 1 https://github.com/rust-lang/crates.io-index.git
cat ta/sk/taskvisor | jq '.versions[] | select(.vers == "0.0.11")'

{
  "name": "taskvisor",
  "vers": "0.0.11",
  "deps": [
    {
      "name": "anyhow",
      "req": "^1.0.100",
      "features": [],
      "optional": false,
      "default_features": true,
      "target": null,
      "kind": "normal"
    },
    {
      "name": "async-trait",
      "req": "^0.1.89",
      "features": [],
      "optional": false,
      "default_features": true,
      "target": null,
      "kind": "normal"
    },
    {
      "name": "dashmap",
      "req": "^6.1.0",
      "features": [],
      "optional": false,
      "default_features": true,
      "target": null,
      "kind": "normal"
    },
    {
      "name": "futures",
      "req": "^0.3.31",
      "features": [],
      "optional": false,
      "default_features": true,
      "target": null,
      "kind": "normal"
    },
    {
      "name": "rand",
      "req": "^0.9.2",
      "features": [],
      "optional": false,
      "default_features": true,
      "target": null,
      "kind": "normal"
    },
    {
      "name": "thiserror",
      "req": "^2.0.16",
      "features": [],
      "optional": false,
      "default_features": true,
      "target": null,
      "kind": "normal"
    },
    {
      "name": "tokio",
      "req": "^1.47.1",
      "features": [
        "rt-multi-thread",
        "macros",
        "time",
        "sync",
        "signal"
      ],
      "optional": false,
      "default_features": true,
      "target": null,
      "kind": "normal"
    },
    {
      "name": "tokio-util",
      "req": "^0.7.16",
      "features": [],
      "optional": false,
      "default_features": true,
      "target": null,
      "kind": "normal"
    }
  ],
  "cksum": "abbe3db14ec7efe5e821af171e0973738cc92e1eeb0141a8e64b7ce61f3fcc25",
  "features": {
    "controller": [],
    "default": [],
    "logging": []
  },
  "yanked": false
}

Conclusion: docs.rs import job failed silently or was skipped for this version.

[evroon]

I wanted to open an issue for this as well for my crate bevy-volumetric-clouds. Looking at the crates.io page with recently added crates, i see that the last created crate for which docs were generated in docs.rs was https://crates.io/crates/ik-mini at 12:17 GMT yesterday (22nd of November).

This PR #3017 seems to have deployed around that time? Could it be related? @syphar

[syphar]

checking it out

[syphar]

all queued again