Affecting Wikimedia as well.

I was away for dinner and indeed, it was imported when I got back and everything seems good.!

Looks like it imported before I got to it. Still seeing an issue?

(I also added you to Community, granting you tremendous new power to tidy up around here.)

Ah! That makes sense. Originally we were more strict about which repositories we would update (which would have caught this) but this created some worse/more-confusing effects in the "enroll" direction (see T10940).

No, there's no load balancer. In DarkConsole under Request -> Machine I'm seeing the same IP for both cases. But repo002 is configured to share the db from repo001.

You can also check Request → Machine in DarkConsole to see which host served things, if the Load Balancer / web node thing might be part of the explanation.

(When I toggle between cluster/no-cluster locally with --service / --remove-service, everything appears to be working properly, although I didn't precisely reproduce your setup.)

Just to rule this out, are repo001 and repo002 also web nodes which may receive traffic directly? That is, could this be explained this way?

Thanks for the report! The primary issue should be resolved at HEAD of master, and promote to stable within about 48 hours.

In T11242#183009, @epriestley wrote:

In T11242#183007, @chad wrote:

{F1706803}

This timely comment saved me a great deal of effort in exporting a high-resolution video of my cat with music and effects or something to get it big enough.

In T11242#183007, @chad wrote:

{F1706803}

Thanks for the ridiculously fast triage. Not an urgent issue for us, just wanted to make sure you were aware of it.

{F1706803}

Appears to only occur when a file needs chunked. Small files work fine.

Several behaviors are interacting here. First, here's how MIME types work:

@csilvers, I think you ran into this too although I wasn't around at the time. Likely fixed in HEAD of master.

Happens on test account too

I tried a couple of other devices in the simulator but couldn't get a repro -- can you try this to get a JS trace?

Let me try my spam account.

Nothing unusual. Latest iPhone/iOS

I can't immediately reproduce this in iOS Simulator or on my physical iPhone 4s. What hardware/OS version are you seeing it on?

I've located the mainframe and uploaded the downloads

@chad: indeed, word-break: break-all on the .differential-diff td element seems to do the trick.

proooobably can just sneak word-break: break-all; in there, but needs some testing.

This is unrelated to prose diffs.

Support Resources has information on how to have general questions answered about Phabricator. Contributing Bug Reports details what information is required for a bug report.

FWIW, the answer to both of your questions before you edited it was yes :p

ignore me - wrong install

Thanks for such a quick response!

Thanks for the report, and for including good reproduction steps.

Thanks for fixing it so quickly!

Thanks for the report, and for including detailed reproduction steps. This should be fixed in HEAD of master, and will promote to stable at the end of the week. Let us know if you run into anything else.

Filed as T11228

Please add the triple dash to the documentation page, I couldn't find it clicking on the main life-saver icon link.

This reproduces for me:

I think the error is correct and the URLs are wrong. We should probably handle this with an Exception though. Also correcting our site links.

Thanks, we'll look into it.

8bb124c37de3dfa29fcd23d4be53a5696b705c81 seems most likely root cause. I can trace it down to ssh coming in from getProtocol which should be blank and give you an error.

I'm not sure what to do with your link. Here's what I can reproduce:

It should be erroring out that you're not putting in a valid URI.

Stock arcanist:

Bug Reports require reproduction steps.

eventually the dead ones appear to fall off the edge, but in the meantime UI doesn't give me a warning that my daemons are not actually running.

Ok, I just installed a new instance of the server in another VM.
Steps to reproduce, as far as I can tell, are:

I identified posts on invalid blogs with this query:

Oh, it actually should cause this issue as currently written. I'm just going to destroy the bad data until this appears in the wild in a more reachable way, I don't think there is any easy way to resolve it.

Post #667 has an invalid blog, so this is probably difficult/impossible for normal users to hit, but it shouldn't cause this issue. I'll see if I can reproduce it locally.

Thanks, this reproduces for me.