I can't reproduce this in production (8f7983a5be3a56db5b79dc7c3a0eb470f1d7ca02):

As a small step towards a more general solution I think it would be very helpful to allow the admins to easily revert changes, where revert means that there will be no traces left of the vandal action after the revert.

@avivey I am exploring that solution as well, I was just wondering if hiding the diff and base tags is a doable solution wanted by the community by large.
We have multiple hosted repositories inter-dependent on each other, and our setup is still in its nascent stage. So I would prefer to not manage duplicate repositories until we finalize on our long term setup.

thanks, I didn't think to use containerPHIDs, I'll give this a go this coming week and let you know if it works for me. Thanks!

Not everything you need here has modern API methods, but I think you can get pretty close:

D17604 adds the six edge types representing relationships between tasks, revisions, and commits to edge.search.

D17603 makes maniphest.search return a "description" field, which looks like this:

Some feedback on this for if it's ever prioritised and picked up again, we've been using this internally for an Unreal Engine 4 based game project's binary assets for about 7 months now, we haven't run into any issues. Works great for us.

If you can run bin/whatever, policies no longer matter since you can bin/storage shell or any other number of dangerous things.

Maybe let bin/search commands target a specific service.

PhabricatorEnv::beginScopedEnv(); works anywhere if this makes more sense as, like, bin/search self-test or something rather than a unit test.

It would be nice to build a practical test suite instead, where we put specific documents into the index and then search for them.

Oh, I'm wrong. It hasn't been removed without replacement: there's a new path option for Elastic. I think there's probably a bug in indexExists() then, since it looks for 'phabricator' by name:

(This is all wrong, see below.)

In T12450#217586, @20after4 wrote:

So I ran into one problem when deploying the latest code to WMF production. We now throw a setup error if we have a cluster with no readable hosts. It actually makes sense to have a cluster that is write-only so that setup error is bogus.

I should also mention that phabricator.allow-email-users is false on this install. Another option to avoid backscatter spam could be to limit the error messages to registered users (maybe even regardless of that setting).

Version is stable, updated about 2 hours ago.

Version?

Thanks to chad for marking my related T12490 as a duplicate.

@dreadlord2203: Why don't you use a different repository for the staging area?

sorry!

I think you need to use your local Phabricator

We have been using Phabricator for a couple of months now and have configured the staging repository to be the same as the Diffusion repository. As mentioned by others we are now facing issues in identifying our release tags due to the immense clutter of the tags. With the virtual ref solution (T8092) still some way off.
Is it possible for starters to update the Diffusion UI to ignore the diff and base tags, so that at minimum the UI clutter is reduced?

Stumbled on this issue while trying to set up my first ever SVN repo through Phabricator. However got it working with the alternate solutions found in Phabrictor documentation itself and online forums(these may be obvious to regular SVN users already).

Yes, after revoking Conduit Access the mirror still works. It's weird... There must've been some other reason why Github rejected my key, unrelated to Conduit.

Duplicate of T10260?

Presumably resolved.

Hello. I just to say what i finded solution.

I can't reproduce this. We mirror from this install without Conduit access enabled, and there is no conceivable reason that Conduit access should need to be enabled for this to work.

ok, that was the problem - default values will cause a field to show up in the 'details' section, thanks!

dubious.

Files now render with a download link, which I think was the core issue here: