Trailing slash

Yeah -- I lean toward thinking that we probably should make bin/auth lock also lock the guidance messages too.

Are we worried about attackers changing the guidance to something like "To prove that your Phabricator account is in use, please email the following link to bob.hackerman@gmail.com and don't read the rest of this email"?

Am I going crazy, or do those methods only handle the "blob fetching" part of this equation? I was looking for examples of the "create a File, do a chunked upload, attach said File to an existing object" flow.

For uploading binary blobs, we'd do the reverse: have the client stream the blob into Files, then call an API method with a reference to the object.

Pop a dialog instead of navigating away.

• Raise "editing while locked" errors in the transaction layer.
• Changed controllers to catch errors and display them reasonably.
• Warn users about locked config when editing existing provider:
  
• When trying to save a provider when the config gets locked during an edit, show reasonable error:
  

Gate auto-login and trust emails.

I was also looking for a way to still render the form, except with all the fields grayed out, since it isn't terribly user-friendly to make someone unlock the config just to see what it already says. This seems tricky though, since there's no AphrontFormView->getChildren() method I can iterate over to call setDisable(true) on.

Thanks for the report. Fixed in D20642, which may or may not land today because of the holiday.

But we could also do it later.

It's turtles all the way down. Computers don't work and all conventions and toolsets are fundamentally broken:

ayyyyy

cd provides "at least once" delivery guarantees.