Ubuntu 16.04 ... is a major platform for Phabricator hosts

T4752 is the detail on that.

Try that?

I think the sequence of action is:

I'm less sure about adding a warning to arc.

I've updated all Phacility cluster hosts which run any git operations (secure*, sbuild*, saux*, repo*) to 2.8.1.

Sorry everyone -- we don't actually read or write this table yet so I didn't add the schema, but the fact that bin/storage adjust would complain slipped my mind. D15744 will fix it and make sure bin/storage adjust is run as part of the test suite.

This is not a demo or test install. Please don't make a mess! You can launch a demo install on Phacility if you want to poke around and try things out.

I think this has come up a couple of times in the past, let me see if I can dig it up.

oh lovely, haha

Kicking this to the daemons should be like 20 lines of code, but we probably also need to flag the file as "queued for deletion" in the UI in the meantime and prevent you from interacting with it, which touches a few other interfaces, so this isn't completely trivial.

Just some cleanup today. New daemon console now shows which hosts daemons are running on:

Cool. Yeah, that all sounds good to me.

(If the current page isn't a Phriction page, I guess just don't mark the thing up?)

That seems reasonable to me. I like using ./ to opt in to this and not making it the default.

From IRC, this may be an issue with older ws (0.7.1) except that I also have 0.7.1 locally. But we should possibly upgrade / recommend upgrading / something like that.

I also tried swapping the ".key" and ".crt" but that gave me the same error as using a bogus file.

Other stuff I tried:

I can't immediately reproduce this...

A terrible workaround is to reload the page before editing.

FWIW, I briefly attempted to fix this while fixing T9348 and gave up.

From IRC, the HTTPS server didn't even start up (no port in netstat). So my first guess is that there's some 'error' handler we need to install, and that should tell us what the issue is (bad SSL key / weird Node stuff / who knows what).

The foundation for this now exists, and core features like browsing user profiles, wiki pages, tasks, etc., appear to work properly in read-only mode.

This is probably fairly straightforward, but I'd like to see some evidence that installs would actually benefit from it before pursuing it.

I vaguely remember these headers really not being very simple last time this came up, too, although maybe I'm misremembering and can't immediately find the discussion.

I think the incidence of this is so low (and should continue to fall in the future) that it's not worth bringing upstream.

Did you guys know that Microsoft is offering a FREE upgrade to Windows 10!
[ Schedule Upgrade NOW ] [ YES! ] [ W-o-w ] [ Reserve Your Windows 10 Today ]

This only affects badges awarded before we began tracking who awarded them. Badges is a prototype application, and I don't think it's worthwhile to maintain code to do something nicer in this case, since the number of affected awards is maybe in the realm of 200 worldwide for all time, of which 80 are on this install.

T6806 might be ripe to resolve one way or another, too.

From T10822, we currently choose [Changed Subscribers] as a stronger action than [Merged] for tasks in some cases in email subject lines. This is probably not the correct heuristic, [Merged] is normally a strong action.

(@eadler's retitle of this bug is fine and I agree that [Merged] should be a stronger action than [Changed Subscribers], I'll make a note about this on T8952.)

We'll take this feedback into account when making future changes to workboards.

When a group of transactions makes several changes, we guess at which change is most likely to be interesting and include that change as the action in the subject line.

This is now in production and appears to be working properly.

Thanks for the report! I think D15719 should fix this; it should be available in master later today and stable in about 24 hours.