https://secure.phabricator.com/book/phabcontrib/article/feature_requests/

Does committing as botusername <anything@anything> definitely not work?

D14390 introduces "ApplicationEditor", which includes more race-resistant controls for editing things like projects and subscribers. In effect, this should merge edits of these fields correctly in all cases where there are no conflicts. Here's an example:

I think this is exceedingly mild/theoretical.

Can you give me a specific scenario where this would be useful?

Upgrade to fe7d8c2.

This same problem exists elsewhere throughout the app.

@chad, do you have any general ideas on what this might look like offhand? It would be good to get a rough first iteration of a direction while I'm tackling ApplicationEditor since all the "generic batch editor" stuff will happen at some point in that process.

Let me get a little further with ApplicationEditor and throw a couple of reference diffs up here before anyone goes crazy with this, since I might still need to change some APIs.

To reproduce:

Actually I guess (2) already got pretty much fixed in D11340.

There are broadly two issues here:

I'm hoping to get this underway in the short term. Before ApplicationEditor actually gets written, we have a longstanding mess in how navigation menus and actions work with the existing ApplicationSearch stuff, roughly captured in T5752.

Thanks for testing the patch, should be in HEAD now. Let us know if you run into anything else.

Oh, sorry, T2950 was itself merged into T3167. Upshot is that we don't plan to change this in the upstream. See also T8227. I think there's a patch on one of those tasks to hack this in locally, but it will be messy/incomplete.

Can you walk me through what commands you used to do your dump/restore? I can't reproduce this problem, and we routinely dump and restore instances in the Phacility cluster.

The upstream pathway for this lies beyond T182.

PEBKAC... I forgot to save my changes to local.json.

Oh, I think I misremembered and it does foreground by default. You can use --background to improve performance, and monitor from /daemon/.

Note that index --all queues stuff into the background, so you may need to wait a while before it finishes. You can use --foreground (slower) or monitor progress from /daemon/ in the web UI.

D14370 likely fixes this, although I don't have ElasticSearch 2.0 locally and haven't tested it. I'd guess this will give you a clean bill of health:

Can you show me the output of this command?

I think the discussion is in T8090.

I think that should clear the way for you, let me know if you hit issues.

D14368 should fix the issue where you're required to set a dummy "Also Clone" repository.

Yeah -- that make sense, I'm just want to be mindful of how much complexity we're adding to the upstream in order to subvert barriers that have no technical reason to exist.

"Lease Host" is not currently expected to work at all. It hasn't been updated for any of the changes, including authorizations. "Lease Working Copy" (under "Drydock") should.

(Yes, I know that Drydock is a prototype... But I figured it's better to file an issue that will be closed as invalid than to not file one at all?)

Drydock is a prototype and all of the Harbormaster build steps which interact with it are prototypes. Much of this code has been substantially rewritten in the last two weeks. See:

If you do this:

Can you show me this?

FWIW this would be useful in repositories where users can push branches (and maybe only to certain regex-matching branch names) and not tags.

There was one more followup in T3855 to fix a couple of bugs, but if you updated this morning you probably picked that up.