This is just a copy of a feature already discussed in T11432, right? Closing this in favor of that, which is already a better and more complete discussion of this request with context.

Moving to a sandbox instance.

Moving to a sandbox instance.

Moving to a sandbox instance.

Moving to a sandbox instance.

Moving to a sandbox SAAS instance.

Moving this to a SAAS sandbox instance.

This isn't a valid bug report (for example, it is missing reproduction instructions). Please see Contributing Bug Reports for help writing bug reports we can accept upstream.

If triggers (described in T5474) would not solve your problem, feel free to file a new feature request describing your problem (see Contributing Feature Requests, Describing Root Problems) and we can discuss approaches.

I think the major intent was being able to edit "View Policy" so you could create private documentation, but I don't recall if we got that far.

I think this is actually for the primary task lists, I just didn't do a good job of describing it. Here are more specific reproduction instructions:

I believe this is fixed in HEAD of master now. Let us know if you're still seeing issues after upgrading.

Broadly, DifferentialCustomField drives a very large amount of stuff in Differential. This was the first generation of custom fields, and is the most complex implementation.

Oh, sorry, maybe you misread? I said "I think I'll have it fixed in a few hours", meaning that I don't expect it to be fixed until later today. Unless you can pull changes from the future, it won't work yet. I'll update this task once things are fixed.

This is related to changes in T11114. I think I'll have it fixed in a few hours.

We're OK with bringing custom build steps for popular platforms upstream, like HarbormasterCircleCIBuildStepImplementation for CircleCI.

I think this is fixed now -- let us know if you're still seeing issues. Thanks for the very thorough report!

I wasn't able to reproduce any hangs or bad behavior from curl locally, but I think D17045 should cause us to select either compression or Content-Length, which is a reasonable thing to expect us to do.

You could also ask Travis for a build.run sort of API. If you're a paying customer of theirs, it might be easier for them to prioritize this request than it is for us to prioritize Travis support. With such an API, there's a fairly straightforward path to Phabricator upstream support.

FWIW, the API seems not intuitive for me: why does the user is able to set arbitrary properties via Conduit, if there is no way to get them back? Is exposing the API actually a hack, to achieve other goals?

Oh, I think the issue is this:

I also can't reproduce this:

Why do you consider this to be a bug, then?

Do you consider this ticket just "make arc patch restore all local commits", or something more?

Oh, that's actually a different task, I don't currently plan to implement that. Let me me rename this to be more clear...

Do we tell you to do this in the documentation anywhere?

This is now better tracked in followups:

This isn't a bug. Diff properties are not intended to be an arbitrary key-value datastore for API consumers.

This field is only populated when you update a revision, and always contains the first line of the update message, which is also posted as a comment.