I think I got all the incredibly dumb, incredibly easy stuff. Plenty of room left, but this install is feeling responsive to me again.

(I think this is fixed, but yell if it happens again.)

Manual runbook on this until we formalize the process, for hypothetical instance turtle:

Do you have rPc2a29338?

That stack trace is bonkers, I think we're calling tput cols every time we update a progress bar.

Phame is a prototype application. See this guide for more information:

I can not reproduce this.

We don't support HHVM. If you can't reproduce this problem on Zend PHP, you should report this compatibility issue to HHVM.

We aren't interested in pursuing changes with no upstream impact.

Feed is doing some pretty silly stuff where it loads transactions, then loads their objects, then loads their handles (which loads their objects again), then loads the objects, then loads handles, which loads the objects again. In some cases, this loads objects about 6x more often than necessary. However, I think this is mostly specific to Feed, and it's not trivial to disentangle. I may take another look tomorrow.

Can you describe the problem you're facing, not just your desired solution? See discussion here for why we consider this to be important:

I believe this is now resolved. Thanks for the report, and sorry for the duplicate mail. I've issued your instance a service credit for the last 48 hours, which will be reflected on your next bill.

Repository tier is restarting now with D13319, so this should be fixed in about a minute.

D13319 should fix this specific issue.

The issue is roughly:

Here's the immediate trace:

(Looking into this now...)

I'm suspicious that this and T8522 may share a root cause (something else being slow) -- unless T8522 evaporated after the database recovery and seems attributable to corruption or ghosts or something.

I'm not sure I understand this problem. What would the "UI option" do? Specifically, I don't know how to implement this option:

I think T6367 effectively made the "logical" vs "physical" separation irrelevant: we can just operate on "physical" messages, since we no longer do any of the weird/bad stuff we used to do when splitting messages. We'll run rules on each "physical" message, but that's desirable and expected. Possibly we'll put some kind of new field on them to tie them all together, but I'm not sure we even need that.

Thanks! Should be fixed in HEAD.

Just to keep this up to date, I had a bunch of other personal/company stuff for the last couple of days so this hasn't moved forward much during that time, although clicking a policy link does show space information now. I have made it most of the way through the "show the strongest policy" thing above, at least, and that'll probably land today.

Odd button alignment on "Notifications":

Here's what I get at HEAD:

@yelirekim, this task has some discussion of why arc land doesn't try to restore state somewhere up above, I'm pretty sure.

I don't expect it to actually "work", per se, today, so this is probably more like "Finish building..."

This is almost certainly a disk error with file permissions. Check the user you're running the daemons as, the repo permissions, etc.

This action should read "Add Subscribers".

This interaction would be less clear in the general case. This problem is better solved through T3670.

T8561 is another case of this, specifically with "Task Description" in Maniphest. Same basic principle as other description fields in other applications.

When you have text selected in a Remarkup text area and click this button:

Sorry, I misunderstood and was using the " Quote menu item on a comment.

Oh! You mean the " symbol above the remarkup text box, right?

I can't reproduce this.

In T8565#121037, @epriestley wrote:

In T8565#121036, @epriestley wrote:

Test.

Test.

In T8565#121036, @epriestley wrote:

Test.

Test.

some well-defined set of "extends" or "inherits" relationships

The vision is for it to be full-featured (e.g., support a variety of languages and input and output formats -- but also support integrations, policies, cheap setup via Harbormaster, easy document preview via arc, etc), but there isn't much demand so progress is likely to be slow. I doubt we'll ever have a superset of Sphinx's features (e.g., I don't know what "ePub" format is and would be slightly surprised to peer into the future and learn that we support it), but the architecture is (mostly) generic.

Development Log

@ostraaten, see T1731 for general mapping of VCS usernames. This is a much more attractive feature than supporting .mailmap, specifically, given the very limited use of .mailmap.

Ah, you're right. Those classes are a little unconventional (we usually don't let subclasses touch properties on the parent class).

Thanks!

• I'm definitely missing advanced search defaulting open, especially on global search. My filter is set to "Open Tasks", which is what I want about 80% of the time, but the other 20% of the time I scroll up to edit the constraints. With the new behavior, I have to open the query interface to do this.

I think these kinds of changes are generally things we're aligned with pursuing.

Oh! Sorry -- I pushed it to this install and put a "give us feedback here" thing on the home page. I can pull it back for now if it's not ready for feedback quite yet, it just looked like most of the internal feedback had been sorted and master was in a pretty good state to merge over.

On the second part, from IRC:

Oh, hovercards have double status, too (note double "Open").

• Line height in Feed and Conpherence feels a little tighter than in comments / descriptions? Maybe I'm imagining this or it's just a size/font/rendering issue, but this feels a touch tighter (mostly vertically, I think?) than I expect:

At first blush: