-
Notifications
You must be signed in to change notification settings - Fork 198
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
Crate failed to build #23
Comments
There is a problem on crates that have |
Indeed, I have seen this warning in my own crates too before. I am not sure there is a way around it, except maybe using a fork of I have also seen crates depending on compiler internals that did not compile with the particular nightly version used. diesel_codegen for example. But I guess making this work is a non-goal. |
https://docs.rs/crate/c-ares-sys/ (and as a result, https://docs.rs/crate/c-ares/ too). Need to install Or, install |
https://docs.rs/crate/probe/ appears to have only attempted a few older versions, which don't work with current nightly, but the current 0.1.6 should be fine. |
@cuviper thanks for reporting. Looks like docs.rs returned IoError when trying to build probe 0.1.4+. I'll fix it tomorrow morning. |
First - cool stuff! :-) Second, about https://docs.rs/crate/dbus/0.3.4
https://docs.rs/crate/alsa/0.1.2 fails with the same error, but missing Is there some way for me as crate author to indicate that docs.rs needs to install these before compiling my crates? Because this seems like it's not going to scale very well as the number of crates grow with the fast-growing Rust ecosystem... |
Thanks for running this service! I noticed that systemd crates fails to build because of missing C development files: https://docs.rs/crate/systemd/0.0.10 This requires libsystemd-dev (or equivalent) on the building machine. By the way, what is the OS of the building environment here? Does it have any package manager that could be re-used to install system dependencies on demand? I'm thinking about using the metadata table to encode this information to drive an external package manager. |
@cuviper for some reason cargo is not generating any documentation when we use @diwic @lucab docs.rs is using Debian. I am planning to add docs.rs metadata table to Cargo.toml, so people can define extra features and system dependencies. BTW I installed systemd development files but looks like systemd crate (or one of its dependency) doesn't work with recent nightly. |
@onur I see you’ve somehow ended up running |
@nagisa I am not sure how to achieve that but I am using |
@onur I filled a rust-lang/cargo#3053. |
https://docs.rs/crate/notify-rust/3.1.1 failed to build, due to the same problems as |
@hoodie docs.rs has rebuilt every version of notify-rust. I was planning to add a button to automate rebuild requests but I changed my mind. People can abuse this kind of feature. |
Perhaps there is a way to authenticate as the crate owner via github? |
@msierks lua crate is looking for lua 5.3.3, and Debian only have lua 5.3.1. There is not much I can do in this case. |
this raises the question, do you build each crate completely or just run |
@hoodie |
@onur hmm, well it appears the next release rust-lua will have lua 5.3.3 bundled with it. Someone correct me if I'm wrong. |
Yes, because in order to generate docs, it has to build the library, thanks to things like |
Thanks for making a great service. https://docs.rs/crate/nodrop-union/0.1.8 simply needs a newer nightly to build. Will it be retried automatically? |
@bluss currently there is no way to trigger rebuilds automatically. I'll upgrade rustc to latest nightly tomorrow. |
Any update on this? |
Great, many thanks! |
docs.rs didn't recognize that I updated my crate Prophet from 0.0.1 to 0.0.2. It is an important update since many things (also documentation) have changed and because I yanked the old version. |
Looks like the crate for glfw is failing to build. Did you guys not install |
Also blingfire is failing because |
https://docs.rs/crate/bitcoin-zmq/0.1.0/builds |
hey there, The Cargo.toml part to control doc.rs behaviour:
|
This build failed due to hitting rust-lang/rust#61804: It looks like the build was with rustc 1.38.0-nightly (95b1fe560 2019-07-20). Would it be possible to update the nightly to pull in the fix for that bug? It was fixed in rust-lang/rust#62086 in nightlies newer than 2019-07-28. |
rustc 1.38.0-nightly (95b1fe560 2019-07-20) also fails to build futures-preview 0.3.0-alpha.18 and crates that depend on it, for issues unrelated with the above mentioned ICE, so an update of the nightly would be great! |
I see the rustc version has been updated, but it looks like crates that have failed before were not rebuilt after the update. (https://docs.rs/crate/futures-io-preview/0.3.0-alpha.18) |
I got this error but I cannot reproduce locally using rustc 1.39.0-nightly (4295eea90 2019-08-30) |
Failed due to missing libmnl-dev |
https://docs.rs/crate/tentacle/0.2.4 These libraries have encountered a problem. They all have 2 features to choose from, but they can't choose all or not noe. The default selection is empty. I don't know how this is expressed in toml metadata, so the doc generation for these libraries has failed.
I know how to config it now. https://docs.rs/about |
Hi, thank you for running Docs.rs! https://docs.rs/crate/clay-core/0.1.0 The build failed due to error: Maybe the problem is in |
@nthend updated the nightly on docs.rs and manually queued a build for your crate! |
Hi! It'd be nice to have docs for my Qt crates ( Ideally, the |
As this docs building. It's obvious that docs.rs does not execute proc-macro-attribute, because each Cloning this repo and executing |
abi_stable and abi_stable_derive are not in the queue/Recent failures/recent releases lists,even though updates of other crates released afterwards were built. Update |
I created a new crate big_enum_set. But the docs are not showing up on docs.rs. Perhaps related? |
We have the same issue with mockiato. No build has been started for version |
Fresh build of [package.metadata.docs.rs]
rustdoc-args = ["--cfg", "procmacro2_semver_exempt"] I wasn't able to find another example yet, but possibly this will crash docs building for any crate with similar configuration. |
@Cerberuser yep, that's indeed a bug in docs.rs. Opened a PR with a fix: #427. Once the PR is merged we will rebuild that crate. |
pgp is failing: https://docs.rs/crate/pgp/0.2.2/builds/187802, but |
How do I know actually if it's a doc-rs problem or not? A single issue on GitHub seems pretty inconvenient for seeking some help... |
@dignifiedquire rebuilt pgp 0.2.2! It was a docs.rs error, but it was fixed a few days ago. @Cerberuser rebuilt |
@pietroalbini Could you trigger a build for |
@pietroalbini Couldn't reproduce the failure myself, so pinging the author - cc @alexcrichton |
@jeremystucki queued both the failed mockiato versions (0.9.3 and 0.9.4) again! |
Hi everyone! It became apparent to us that this issue doesn't really scale: people posting here start receiving useless notifications and need to manually unsubscribe from the thread, and it's hard for us to keep track of which crates are fixed and which need action from our end. We now recommend everyone to create a separate issue for each crate, and to aid that we added issue templates for broken crates and sandbox limit increase requests, changing the website to point to them. This issue will be also locked to prevent further reports here. If your crate still fails please open a new issue and we'll look into it! |
Docs.rs may have failed to build some crates for various reasons (missing dependency on build machine or bad configuration etc).
You can report them into this issue.
The text was updated successfully, but these errors were encountered: