Quoting for the main page :

This problem is probably the same as the one in task T10120. This is probably related to caching since clearing the cache restore the functionnality (at least for some times).
However, in our case, we have a regular httpd server without any mods installed.
Do you have any ideas of how we could debug that ?

Indeed, the case seems to be connected with caching. If the browser cache is cleared and the project manage page is reloaded the policy-rule-editor is indeed found and a custom policy can be edited. However, this occurs only once. When the page is reloaded, or if another project is edited afterwards the issue is back - and can be remedied by emtying the cache, again.

For everyone who would like to use this feature (Taking of course the above mentioned security risks into account).

We use a custom field release description of type remarkup. We then export tasks via conduit API to our HTML release notes. In this release description we use some of the remarkup feature set.

@avivey to close the loop -- global rules worked perfectly. Thanks again!

See Support Resources for more information, or more specifically https://secure.phabricator.com/book/phabricator/article/support/#community.

Got it, thanks. Moved this to a Ponder question.

I think you want Ponder for general help and assistance with Phabricator.

Here's my process thus far:

1. Configuring System User Accounts
   • Create 3 users, one for daemons, web server, and version control.
   • sudo visudo to give web server ad version control users the ability to sudo to daemon user.
   • Edit /etc/passwd and /etc/shadow ... FAIL???
2. Switch SSH to port 222 (this was actually super simple)
   • Edit /etc/services, search for ssh, change port references from 22 to 222. In System Preferences disabling and reenabling remote login under the sharing section causes the changes to take effect.
3. set phd.user and diffusion.ssh-user (simple).
4. Setting up the new sshd configuration. This is essentially the same. One thing to note is users will have to disable the new Integrity (rootless) feature of Mac OX El Capitan if they wish to use the recommended directories (i.e. /usr/libexec). Otherwise a different directory works fine.

I guess "off" is default, so "disabled" isn't quite accurate.

From elsewhere, it sounds like there isn't driving interest in pursuing this.

The expectation with the git fetch in question is that it will run very frequently on active repositories, so we should have all but the last few minutes (or even seconds) of data in most cases, and almost all the refs should be identical to the remote refs. The fetch schedule is here, but for enabled repositories we'll never wait more than 6 hours between fetches:

Hi. I work with @eadler. I didn't do the initial analysis, but I have some familiarity with the issue.

I also can't immediately reproduce the root issue. Here's what I did:

I think I got 'em all, but let me know if you catch any more.

Thanks :)

This seems to be happening consistently for all new commits.

In T10368#161308, @epriestley wrote:

The other part of the root problem is: why do you have 10K refs? Can you just archive 9,800 of them to avoid this problem, particularly if you only care about master?

We don't rely on regex() for import only on the repository in question. We do use it for other repos, but we aren't concerned about them due to their relatively small size.

The points in project really look like project tag, I found that a little confusing.

In T10368#161308, @epriestley wrote:

If there's no technical reason git has to be slow, we may just be able to fix git.

Broadly, here are the general issues we've currently seen with Diffusion URIs:

Someone on Facebook noted that I omitted the Cyclone. Eek!

You spoke to the "Track Only" stuff a little bit in the description -- for complete clarity, we have two separate options that are only sometimes available:

Oh, sorry, yeah -- for macros, you'd currently have to pick the file off your desktop with the file picker thing. I'm thinking more about a general "select some existing file" feature for other cases like cover images, where you can drag-and-drop.

Before pursuing this, I'd like to develop a better understanding of the root problem. Particularly:

ah, I misunderstood @epriestley's comments above.

We don't offer drag and drop upload on the Macro page. :(

You got all of the mineral costs correct!