Skip to content
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 4 pull requests #85560

Merged
merged 12 commits into from
May 21, 2021
Merged

Rollup of 4 pull requests #85560

merged 12 commits into from
May 21, 2021

Conversation

GuillaumeGomez
Copy link
Member

Successful merges:

Failed merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

LeSeulArtichaut and others added 12 commits May 20, 2021 00:01
This bug was only visible on mac. Also, print_step_rusage is a relatively new
internal feature, that is not heavily used, and has no tests. All of these
factors contributed to how this went uncaught this long. Thanks to Josh Triplett
for pointing it out!
…r=jsha

Reset "focusedByTab" field when doing another search

Fixes rust-lang#85467.

The problem was simply that we forget to reset the `focusedByTab` field, which was still referring to removed DOM elements.

r? ``@jsha``
Remove dead toggle JS code

Explanations on how I got there: I randomly saw `adjustToggle` while browsing through code, checked where it was called, put a `debugger;` instruction in it and checked on all pages while playing with settings and toggles. The breakpoint was never triggered. I then looked at `collapseNonInherent` (its grand-parent). In there, the breakpoint was triggered so I look at what was being done and in fact... nothing. So I simply removed it all, re-ran the tests and play with the UI. Everything is working as expected.

Better double check in case I forgot to check a case though, but if nothing has been left out, then it's a great cleanup once again. :)

r? ``@jsha``
…c, r=Mark-Simulacrum

facepalm: operator precedence fail on my part.

This bug was only visible on mac. Also, print_step_rusage is a relatively new
internal feature, that is not heavily used, and has no tests. All of these
factors contributed to how this went uncaught this long. Thanks to Josh Triplett
for pointing it out!
…komatsakis

Check for more things in THIR unsafeck

Reunion of rust-lang#85306, rust-lang#85381 and rust-lang#85419 with conflicts resolved.
r? `@nikomatsakis`
@rustbot rustbot added the rollup A PR which is a rollup label May 21, 2021
@GuillaumeGomez
Copy link
Member Author

@bors: r+ p=4 rollup=never

@bors
Copy link
Contributor

bors commented May 21, 2021

📌 Commit 0f48e63 has been approved by GuillaumeGomez

@bors bors added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label May 21, 2021
@bors
Copy link
Contributor

bors commented May 21, 2021

⌛ Testing commit 0f48e63 with merge 5dc8789...

@bors
Copy link
Contributor

bors commented May 21, 2021

☀️ Test successful - checks-actions
Approved by: GuillaumeGomez
Pushing 5dc8789 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label May 21, 2021
@bors bors merged commit 5dc8789 into rust-lang:master May 21, 2021
@rustbot rustbot added this to the 1.54.0 milestone May 21, 2021
@GuillaumeGomez GuillaumeGomez deleted the rollup-8k90rc7 branch May 22, 2021 09:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merged-by-bors This PR was explicitly merged by bors. rollup A PR which is a rollup S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants