I'm just going to merge this into T9548 since I think bundle2 support will fix it?

I believe this was resolved by the introduction of the "query overheating" mechanism, described in T11773.

I'm going to merge this into T5815, which is a more general discussion of action queues.

I can't reproduce this; we can't move forward without reproduction steps.

I'm just going to merge this into T10448, this task doesn't have anything not already covered there.

• DiffusionCommitQuery has had the "good" version for a while.
• We're nuking Releeph at some point.

T12089 has a narrower description with some screenshots, I think the behavior got flipped by accident.

The "Ambiguous Leaders" section in the docs should more or less cover this, and using bin/repository thaw to promote your favorite node to leadership is probably the easiest way to resolve it. This pathway to ambiguity is fairly mundane compared to what the documentation imagines, though, and both clusterize and that UI warning could point toward bin/repository thaw --promote. I'll make these more clear.

Thanks, not intentional.

I can't reproduce this either. Here's:

Alright. If we don't hear back from you in a few days we'll close this since we can't move forward on it, but you're free to file a new task when you're ready to move forward.

I can't reproduce this, and I suspect it was fixed some time ago during changes related to T6027.

Oh, one final note:

I've collected some guidance more formally in T12085.

I've also made these additional changes, not directly related to the original request:

I think this is mostly guidance I neglected to issue, sorry about that.

Thanks! D17162 should clean this up.

These changes are now available in HEAD of master, and should be available on stable after Jan 13. master is also safe to upgrade into right now, although some T11114 stuff may churn later this week.