Uh oh!
There was an error while loading. Please reload this page.
Update book - #47753
Conversation
rust-highfive
commented
Jan 25, 2018
(rust_highfive has picked a reviewer for you, use r? to override) |
alexcrichton
commented
Jan 25, 2018
in terms of r+, r=me whenever this is good to go! I imagine though @rust-lang/docs may wish to help out with the investigation |
QuietMisdreavus
commented
Jan 25, 2018
I can confirm the reference rendering strangely. There's an open PR on the reference that might help with this; should we merge that first and update it here? |
Michael-F-Bryan
commented
Jan 26, 2018
You'll probably want to make sure each document's Let me know if there's anything we can do from |
a9268e3 to
33b32f0Comparesteveklabnik
commented
Jan 26, 2018
This will fail until rust-lang/mdBook#585 is in an mdbook release. |
33b32f0 to
d319ba2Comparesteveklabnik
commented
Jan 27, 2018
this should be good to go now 🎊 |
alexcrichton
commented
Jan 27, 2018
Looks like Travis may be failing? |
steveklabnik
commented
Jan 27, 2018
Hm. very odd. not super helpful... |
Michael-F-Bryan
commented
Jan 28, 2018
Lol. We're using /// Prints a "backtrace" of some `Error`.pubfnlog_backtrace(e:&Error){error!("Error: {}", e);for cause in e.iter().skip(1){error!("\tCaused By: {}", cause);}} |
@Michael-F-Bryan yeah, sorry, I typed that in haste; this behavior is totally reasonable! I've pushed a commit that uses this, let's see what it says (the build succeeds for me locally) |
7fe8313 to
dd32a11Comparesteveklabnik
commented
Jan 28, 2018
i was able to reproduce locally, and this is what I have: this make sense as to why it's only the reference that fails. note that i wonder if this is an mdbook bug, not respecting the path when passed in |
steveklabnik
commented
Jan 28, 2018
Yes, this is the answer, I believe. The reference has |
Before, when someone like the Reference set their extra css as "theme/reference.css" in their book.toml, this path would be treated as relative to the invocation of mdbook, and not respect the input path. This PR modifies these relative paths to do so. Fixes the build of rust-lang/rust#47753 which blocks updating rustc to mdbook 0.1
steveklabnik
commented
Jan 28, 2018
dd32a11 to
84f2111Comparesteveklabnik
commented
Jan 28, 2018
confirmed the fix locally, but pushed a commit up here to check on the builders too we'll need an mdbook release in order to ship this |
steveklabnik
commented
Jan 28, 2018
well, uh looks like that's another bug: https://travis-ci.org/rust-lang/rust/builds/334450214#L2554 |
steveklabnik
commented
Jan 30, 2018
okay! I'm going to wait until the release ships, and then rebase this to be more reasonable. |
steveklabnik
commented
Feb 3, 2018
Why is it invalid? In that we don't accept MPL based code? I was pretty sure we had some already... and it would be kinda weird to reject Mozilla's license, heh. |
kennytm
commented
Feb 3, 2018
@steveklabnik it would be invalid if these packages were used by the standard library since it should be strictly MIT/Apache2. As these are only used for generating the book, you can add exceptions to tidy by editing https://github.com/rust-lang/rust/blob/master/src/tools/tidy/src/deps.rs |
steveklabnik
commented
Feb 3, 2018
new commit pushed, that look correct? :) |
kennytm
commented
Feb 3, 2018
@bors r=alexcrichton |
bors
commented
Feb 3, 2018
📌 Commit abb162c has been approved by |
…chton Update book This PR does two things: 1. update the book to include rust-lang/book#1088 2. update to mdbook 0.1 Both of these things are big changes, so I want to land them now, well before the next branch, so we can kick the tires. ------------------------------ Locally, I'm seeing some weirdness around the reference and this:  Putting this PR up so others can try and build and see if it reproduces for them.
…chton Update book This PR does two things: 1. update the book to include rust-lang/book#1088 2. update to mdbook 0.1 Both of these things are big changes, so I want to land them now, well before the next branch, so we can kick the tires. ------------------------------ Locally, I'm seeing some weirdness around the reference and this:  Putting this PR up so others can try and build and see if it reproduces for them.
bors
commented
Feb 4, 2018
☔ The latest upstream changes (presumably #47991) made this pull request unmergeable. Please resolve the merge conflicts. |
and improve printing of errors
abb162c to
983cc00Comparesteveklabnik
commented
Feb 4, 2018
@bors r=alexcrichton |
bors
commented
Feb 4, 2018
📌 Commit 983cc00 has been approved by |
…chton Update book This PR does two things: 1. update the book to include rust-lang/book#1088 2. update to mdbook 0.1 Both of these things are big changes, so I want to land them now, well before the next branch, so we can kick the tires. ------------------------------ Locally, I'm seeing some weirdness around the reference and this:  Putting this PR up so others can try and build and see if it reproduces for them.
* Handle input path with regards to custom css Before, when someone like the Reference set their extra css as "theme/reference.css" in their book.toml, this path would be treated as relative to the invocation of mdbook, and not respect the input path. This PR modifies these relative paths to do so. Fixes the build of rust-lang/rust#47753 which blocks updating rustc to mdbook 0.1 * don't use file-name the style name is theme/reference.css, this results in a Err(StripPrefixError(())), which means that we push only the file_name, losing the theme bit
This PR does two things:
Both of these things are big changes, so I want to land them now, well before the next branch, so we can kick the tires.
Locally, I'm seeing some weirdness around the reference and this:
Putting this PR up so others can try and build and see if it reproduces for them.