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:

Sounds like this is resolved.

We get the same bug, except that it's worse because when you enlarge the file list, the splitter moves, reducing the available area for viewing the diff, but the scrollable file list doesn't get any wider! You still can't see the full filenames, which is what you wanted in the first place.

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.

@cos: probably should not have a default value.

ok, so the intent is that any initialized field shows up in details, but no others? If so, then do fields with default values show-up? I have a software version field for example has a default of 0.0.0 and it shows up for subtypes for which it's hidden. Here are some screenshots to show you:

We currently display the description in the reports we generate and those reports are themselves markdown, our tools currently upload these docs to phriction.

A SAAS install is hitting the "move + rename binary" case.