-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Rollup of 6 pull requests #47492
Rollup of 6 pull requests #47492
Conversation
GuillaumeGomez
commented
Jan 16, 2018
- Successful merges: Test rustdoc js #47250, fix faulty comment #47302, Report errors instead of panic!() when linkcheck encounters absolute paths #47387, Switch to pulldown as default markdown renderer #47398, Update html-diff crate => fix unicode parsing and invalid paths #47436, Don't include bang in macro replacement suggestion #47444
- Failed merges:
When we suggest the replacement for a macro we include the "!" in the suggested replacement but the span only contains the name of the macro itself. Using that replacement would cause a duplicate "!" in the resulting code. I originally tried to extend the span to be replaced by 1 byte in rust-lang#47424. However, @zackmdavis pointed out that there can be whitespace between the macro name and the bang. Instead, just remove the bang from the suggested replacement. Fixes rust-lang#47418
…ark-Simulacrum Test rustdoc js Add tests for the rustdoc search. It was heavily required because of all the recent breaking changes that happened while I went through improvements in doc search (add search in/for generic search for example).
…ster fix faulty comment after rust-lang#43506 there is no fixed number of request sent.
…teveklabnik Report errors instead of panic!() when linkcheck encounters absolute paths The RBE contained some absolute links that failed the link check in rust-lang#46196. Diagnosing these issues was needlessly complicated, thanks to the linkchecker just panicing instead of reporting proper errors. This PR replaces the panic with a proper `*errors = true` + error message handling. The linkchecker itself doesn't have any tests so I intentionally didn't touch anything else than the code that previously did the `panic!()`. A small code quality improvement might be made by binding the `Path::new(base).join(url)` into a variable before the for-loop and using this resolved url in both the for loop and the error message. r? @steveklabnik (If not for any other reason than having r on the rust-lang#46196.)
…=QuietMisdreavus Switch to pulldown as default markdown renderer r? @QuietMisdreavus
…tMisdreavus Update html-diff crate => fix unicode parsing and invalid paths r? @QuietMisdreavus
…suggestion, r=estebank Don't include bang in macro replacement suggestion When we suggest the replacement for a macro we include the "!" in the suggested replacement but the span only contains the name of the macro itself. Using that replacement would cause a duplicate "!" in the resulting code. I originally tried to extend the span to be replaced by 1 byte in rust-lang#47424. However, @zackmdavis pointed out that there can be whitespace between the macro name and the bang. Instead, just remove the bang from the suggested replacement. Fixes rust-lang#47418 r? @estebank
Some changes occurred in HTML/CSS. |
r? @aturon (rust_highfive has picked a reviewer for you, use r? to override) |
@bors: r+ p=1 |
📌 Commit 83b8946 has been approved by |
💔 Test failed - status-appveyor |
It's been more than 8 hours now. I suppose there's a problem... |
@GuillaumeGomez https://www.traviscistatus.com/incidents/c1s4dlyxd4lf Nothing will start even if we retry. |
💔 Test failed - status-travis |
Well, let's just wait then... |
🤔 In #47035 the half of the jobs are running. Travis's incident report is still active, so not sure if that's normal. Anyway we should just close this and create a new rollup. There are 40 approved PRs out there waiting -_- |