-
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
Include both md and yaml ICE ticket templates #106898
Conversation
* Existing compilers link to the md version * The YAML version field for the backtrace *doesn't let us paste a full backtrace* * We will need the YAML version in order to be able to submit reports once we start storing the backtrace to disk
(rustbot has picked a reviewer for you, use r? to override) |
r=me, but I'm confused about keeping both. Isn't that likely to be confusing for users? |
@Mark-Simulacrum it is (which is why I removed the previous one), but there are conflicting desires here:
An option would be to make the yaml one into "Automatic ICE" or "Tool Only ICE report" or something like this. I'm not happy with this situation, and if I didn't dislike the md templates because of how unintuitive they can be I'd be reverting outright. |
I think this would be my preference, personally, if we expect it to be primarily used by the auto-filled link. |
@rustbot author (not sure if you want to go ahead here or not) |
@bors r=Mark-Simulacrum Lets merge this now because it is causing trouble to users. I will be unavailable for another couple of weeks, I had to deal with a sudden personal issue. Would you mind following up on this @Mark-Simulacrum? |
I'll try to add it to my list. |
@bors rollup |
… r=Mark-Simulacrum Include both md and yaml ICE ticket templates * Existing compilers link to the md version * The YAML version field for the backtrace *doesn't let us paste a full backtrace* * We will need the YAML version in order to be able to submit reports once we start storing the backtrace to disk Follow up to rust-lang#106831. Reaction to rust-lang#106874, which made me realize that *really* long backtraces are rejected by GitHub Forms. A single backtrace won't hit this, but ICEs sometimes compound.
…llaumeGomez Rollup of 12 pull requests Successful merges: - rust-lang#106898 (Include both md and yaml ICE ticket templates) - rust-lang#107331 (Clean up eslint annotations and remove unused JS function) - rust-lang#107348 (small refactor to new projection code) - rust-lang#107354 (rustdoc: update Source Serif 4 from 4.004 to 4.005) - rust-lang#107412 (avoid needless checks) - rust-lang#107467 (Improve enum checks) - rust-lang#107486 (Track bound types like bound regions) - rust-lang#107491 (rustdoc: remove unused CSS from `.setting-check`) - rust-lang#107508 (`Edition` micro refactor) - rust-lang#107525 (PointeeInfo is advisory only) - rust-lang#107527 (rustdoc: stop making unstable items transparent) - rust-lang#107535 (Replace unwrap with ? in TcpListener doc) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
…te, r=estebank Clearly signal purpose of the yaml template Following up on rust-lang#106898 (comment)
…te, r=estebank Clearly signal purpose of the yaml template Following up on rust-lang#106898 (comment)
Follow up to #106831. Reaction to #106874, which made me realize that really long backtraces are rejected by GitHub Forms. A single backtrace won't hit this, but ICEs sometimes compound.