{"action":"created","issue":{"url":"https://api.github.com/repos/rust-lang/rust/issues/51468","repository_url":"https://api.github.com/repos/rust-lang/rust","labels_url":"https://api.github.com/repos/rust-lang/rust/issues/51468/labels{/name}","comments_url":"https://api.github.com/repos/rust-lang/rust/issues/51468/comments","events_url":"https://api.github.com/repos/rust-lang/rust/issues/51468/events","html_url":"https://github.com/rust-lang/rust/issues/51468","id":330944792,"node_id":"MDU6SXNzdWUzMzA5NDQ3OTI=","number":51468,"title":"`cargo doc` fails for the h2 crate (v0.1.9) on nightly 2018-06-05","user":{"login":"jimmycuadra","id":122457,"node_id":"MDQ6VXNlcjEyMjQ1Nw==","avatar_url":"https://avatars2.githubusercontent.com/u/122457?v=4","gravatar_id":"","url":"https://api.github.com/users/jimmycuadra","html_url":"https://github.com/jimmycuadra","followers_url":"https://api.github.com/users/jimmycuadra/followers","following_url":"https://api.github.com/users/jimmycuadra/following{/other_user}","gists_url":"https://api.github.com/users/jimmycuadra/gists{/gist_id}","starred_url":"https://api.github.com/users/jimmycuadra/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jimmycuadra/subscriptions","organizations_url":"https://api.github.com/users/jimmycuadra/orgs","repos_url":"https://api.github.com/users/jimmycuadra/repos","events_url":"https://api.github.com/users/jimmycuadra/events{/privacy}","received_events_url":"https://api.github.com/users/jimmycuadra/received_events","type":"User","site_admin":false},"labels":[{"id":203738,"node_id":"MDU6TGFiZWwyMDM3Mzg=","url":"https://api.github.com/repos/rust-lang/rust/labels/T-rustdoc","name":"T-rustdoc","color":"bfd4f2","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2018-06-10T06:39:38Z","updated_at":"2018-07-03T16:40:40Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"```\r\n$ rustup show\r\nDefault host: x86_64-apple-darwin\r\n\r\ninstalled toolchains\r\n--------------------\r\n\r\nstable-x86_64-apple-darwin\r\nnightly-x86_64-apple-darwin (default)\r\n\r\nactive toolchain\r\n----------------\r\n\r\nnightly-x86_64-apple-darwin (default)\r\nrustc 1.28.0-nightly (4a9c58c6b 2018-06-05)\r\n$ cargo doc -p h2\r\n Documenting h2 v0.1.9\r\nwarning: [u8] cannot be resolved, ignoring it...\r\n  --> /Users/example/.cargo/registry/src/github.com-1ecc6299db9ec823/bytes-0.4.8/src/lib.rs:1:1\r\n   |\r\n1  | / //! Provides abstractions for working with bytes.\r\n2  | | //!\r\n3  | | //! The `bytes` crate provides an efficient byte buffer structure\r\n4  | | //! ([`Bytes`](struct.Bytes.html)) and traits for working with buffer\r\n...  |\r\n68 | | //! perform a syscall, which has the potential of failing. Operations on `Buf`\r\n69 | | //! and `BufMut` are infallible.\r\n   | |________________________________^\r\n   |\r\n   = note: the link appears in this line:\r\n\r\n            A `Bytes` handle can be created directly from an existing byte store (such as &[u8]\r\n                                                                                            ^^\r\n\r\nwarning: [cfg] cannot be resolved, ignoring it...\r\n  --> /Users/example/.cargo/registry/src/github.com-1ecc6299db9ec823/cfg-if-0.1.3/src/lib.rs:1:1\r\n   |\r\n1  | / //! A macro for defining #[cfg] if-else statements.\r\n2  | | //!\r\n3  | | //! The macro provided by this crate, `cfg_if`, is similar to the `if/elif` C\r\n4  | | //! preprocessor macro by allowing definition of a cascade of `#[cfg]` cases,\r\n...  |\r\n26 | | //! # fn main() {}\r\n27 | | //! ```\r\n   | |_______^\r\n   |\r\n   = note: the link appears in this line:\r\n\r\n            A macro for defining #[cfg] if-else statements.\r\n                                   ^^^\r\n\r\nwarning: [cfg] cannot be resolved, ignoring it...\r\n  --> /Users/example/.cargo/registry/src/github.com-1ecc6299db9ec823/cfg-if-0.1.3/src/lib.rs:1:1\r\n   |\r\n1  | / //! A macro for defining #[cfg] if-else statements.\r\n2  | | //!\r\n3  | | //! The macro provided by this crate, `cfg_if`, is similar to the `if/elif` C\r\n4  | | //! preprocessor macro by allowing definition of a cascade of `#[cfg]` cases,\r\n...  |\r\n26 | | //! # fn main() {}\r\n27 | | //! ```\r\n   | |_______^\r\n   |\r\n   = note: the link appears in this line:\r\n\r\n            This allows you to conveniently provide a long list #[cfg]'d blocks of code\r\n                                                                  ^^^\r\n\r\nwarning: [Debug] cannot be resolved, ignoring it...\r\n   |\r\n   = note: the link appears in this line:\r\n\r\n            themselves through the [`Display`] and [`Debug`] traits, and may provide\r\n                                                    ^^^^^^^\r\n\r\nerror[E0658]: access to extern crates through prelude is experimental (see issue #44660)\r\n  |\r\n  = help: add #![feature(extern_prelude)] to the crate attributes to enable\r\n\r\nerror: Could not document `h2`.\r\n\r\nCaused by:\r\n  process didn't exit successfully: `rustdoc --crate-name h2 /Users/example/.cargo/registry/src/github.com-1ecc6299db9ec823/h2-0.1.9/src/lib.rs -o /Users/example/example-cargo-project/target/doc -L dependency=/Users/example/example-cargo-project/target/debug/deps --extern byteorder=/Users/example/example-cargo-project/target/debug/deps/libbyteorder-df3eee4befa1312c.rmeta --extern bytes=/Users/example/example-cargo-project/target/debug/deps/libbytes-9fc866f4058b4096.rmeta --extern fnv=/Users/example/example-cargo-project/target/debug/deps/libfnv-2278a5d27eb0baf9.rmeta --extern futures=/Users/example/example-cargo-project/target/debug/deps/libfutures-5c1e38662d6f78e5.rmeta --extern http=/Users/example/example-cargo-project/target/debug/deps/libhttp-b2084a070c91801e.rmeta --extern indexmap=/Users/example/example-cargo-project/target/debug/deps/libindexmap-fbca607fdf3e2794.rmeta --extern log=/Users/example/example-cargo-project/target/debug/deps/liblog-1c027577d3857644.rmeta --extern slab=/Users/example/example-cargo-project/target/debug/deps/libslab-4299e706602486cd.rmeta --extern string=/Users/example/example-cargo-project/target/debug/deps/libstring-1c5b00744b69ff86.rmeta --extern tokio_io=/Users/example/example-cargo-project/target/debug/deps/libtokio_io-79182f96ea980954.rmeta` (exit code: 101)\r\n```"},"comment":{"url":"https://api.github.com/repos/rust-lang/rust/issues/comments/402220012","html_url":"https://github.com/rust-lang/rust/issues/51468#issuecomment-402220012","issue_url":"https://api.github.com/repos/rust-lang/rust/issues/51468","id":402220012,"node_id":"MDEyOklzc3VlQ29tbWVudDQwMjIyMDAxMg==","user":{"login":"cramertj","id":5963049,"node_id":"MDQ6VXNlcjU5NjMwNDk=","avatar_url":"https://avatars1.githubusercontent.com/u/5963049?v=4","gravatar_id":"","url":"https://api.github.com/users/cramertj","html_url":"https://github.com/cramertj","followers_url":"https://api.github.com/users/cramertj/followers","following_url":"https://api.github.com/users/cramertj/following{/other_user}","gists_url":"https://api.github.com/users/cramertj/gists{/gist_id}","starred_url":"https://api.github.com/users/cramertj/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cramertj/subscriptions","organizations_url":"https://api.github.com/users/cramertj/orgs","repos_url":"https://api.github.com/users/cramertj/repos","events_url":"https://api.github.com/users/cramertj/events{/privacy}","received_events_url":"https://api.github.com/users/cramertj/received_events","type":"User","site_admin":false},"created_at":"2018-07-03T16:40:40Z","updated_at":"2018-07-03T16:40:40Z","author_association":"MEMBER","body":"@GuillaumeGomez It's a great thing that rustdoc can issue warnings, but it shouldn't block the creation of docs. That is, for an upstream with `#![deny(warnings)]`, there is *no way* to generate documentation for it when a new warning is added and the doc generation breaks."}}
{"actor":{"display_login":"cramertj"}}