Basically any time you could use Projects + Owners + Herald to be more tactical and less shotgun-like in assigning reviews is likely much more beneficial to correct coverage and lessening workload.

Neat thanks! That does look like it would help with our problem but I still think that expanding a group would be a useful feature.

I want to say Pinterest had a similar workflow and built a custom herald rule to manage it, not sure if that sounds interesting to you: https://engineering.pinterest.com/blog/shipping-faster-new-pr-processing-system

One reason it pops up is that we put all develops as reviewers and then when one person actually decides to claim it for review they remove everyone else. We put all developers as subscribers, though, so that everyone stays notified when things change. I often want to remove myself as a subscriber so that I don't get emails about revisions I don't care about.

This feels bad in general that you would need such a feature. For example, if I'm not qualified to review something, I just don't and it has no effect to my daily flow. Can you go into more detail about why your getting so many review requests you shouldn't be getting and how your using Dashboards perhaps to keep track of stuff that you actually should be reviewing?

The API documentation is not clear for implement a conduit client using JavaScript.

The conduit app has examples on calling conduit using cURL - you should be able to translate that to javascript.

Yeah the way that flow works is real dumb / undiscoverable / confusing / hard to use right now. It works great if you know the secret magic, but the secret magic is pretty secret.

Ah you just connected the dots for me about how to create custom queries for Dashboards.

There's some discussion of the behavior of limits in T9372#175512 / D15923.

Ah hah, I had a limit of 5 set. I'd assumed that meant "5 per bucket". I see now that it means "5 results across all buckets".

What query is the query panel actually executing? Does it look exactly like this?

Strategy I'm pursuing (for Git) is:

You can email me directly at epriestley@phacility.com, or create a private thread in Conpherence on this install via the icon in the header.

I worked on this problem for a couple hours last night, tailing log files
and checking various security features. This is our development server, the
lead Dev and I have complete control over it. I also had this problem on
another machine which is setup very similarly (CloudLinux, but locked done
a ton as its our hosting server), but on that machine I did not put the
Phabricator installation in a cPanel account. Had the same problem there,
so I don't think it's the security / CageFS getting in the way. Something
is timing the script out or killing it, and it's not the Kernel.

This needs to be the default behavior. For example, if you update lib-important-security/ and the new version has a bug which causes it to fatal, Phabricator must also fatal. It is not acceptable to just skip the extension and start without loading a library that may have important security/policy code an install could rely on, because this could make the install vulnerable to security or policy threats which you expect to be protected from.

Extensions are a really advanced feature, and you will get almost no support from upstream here if you have them installed. Or another way, anyone who is installing extensions should know Phabricator well enough to know how to fix this issue manually (hand editing local.json).

In T10349#160861, @chad wrote:

Maybe a config option to make your own regex for display?

@hach-que Perhaps the terminology isn't really consistent then. When I add a project to an edit, it appears under a heading called "tags". Perhaps the Herald rule should say "tagged with"

项目权限管理问题：在建立项目后，创建人可以编辑项目描述，可以设置“修改描述”的权限，这次遇到问题就是这个配置是Editable By Project Members修改成 Editable By
和飞信_手机 问题解决。

In T10779#177063, @CodeMouse92 wrote:

Confirmed workaround: set base project edit permissions to something other than Project Members.

I'm going to merge this into T5267, which discusses a larger-scale effort to translate Phabricator in the relatively near term. We'll be interested in feedback like this once that's a little further along.

I think we've shot down other requests in this vein (Herald + Workboards) due to overwhelming interest in T5474, which would likely be prohibitive or insanely complicated to support if Herald was in the mix.

I'm going to merge this into T5267, which is more actionable in the short term.

I was kind of expecting that 'cluster.read-only' would be a database configuration value, not a local configuration value. Otherwise you need to update all nodes in the cluster instead of just setting the flag in the DB. My expectation when the cluster DB is read-only is that only the following operations work:

@aristedes It means projects and subscribers of the commit. For example, you can add those projects here:

Subscribers -> Are these watchers or members of the project? I don't recognise the word "subscribers" in Phabricator.

It confused at least one person, but I am relatively new to this product.

The trouble is that that could sometimes give the wrong answer, because querying the Git URI is not the only way that arc itself finds the repository; for example, the repository callsign can be hardcoded into .arcconfig.

I think the only way right now is to get the remote uri, call repository.query with it, and parse that.
It might make sense to just teach arc which to output it's things in json.

I think I didn't actually do these things, I did a different and more horrible set of things and then wrote these great instructions to avoid all the msitakes I made. I'll attempt to let dump pierce through read-only, or find some other solution if that isn't straightforward.

Should be fixed in HEAD of master. Thanks for the report!

Ah! I got a repro.

Sorry, the Root Problem would be something like:

• Entirely unset mysql.host
• Configure a master and a replica in cluster.databases
• Go to /config/database/

I can't immediately reproduce this. Here's things running fine with mysql.host set to a bogus value:

(I marked D15981 as fixing this but I'm going to leave it open for confirmation since I'm not completely sure there weren't more cases that I missed.)

After you created the second URI, you can switch the first one to active IO back, so there the error messages does not work:

T6102 and the downstream also contain discussion of a second case which does center around exact matches -- searching for "Wikidata" -- but I can't reproduce it at HEAD:

Strange. I tried it again, now I can't reproduce it too, but the history said, that I didn't make a fault.

I can't reproduce this. Here's the first repository (I/O off, disabled);

D15981 doesn't, strictly speaking, prioritize exact matches. However, it should fix the underlying issue.

This seems related to T5474: Support workboard column triggers which activate when a task is dropped into a column.

I think anything automatic here would likely only be truly correct maybe 50% of the time, and I think that's really bad from an accuracy perspective if that's what's important to your company. I'd rather look at what information is actually missing from the workboard cards (ie, diff attached) and explore options there.

I don't understand the root problem this is seeking to solve. Please read Describing Root Problems carefully and try to follow the instructions there to describe a problem we can solve.

Thank you very much !

To edit project tags for a repository, navigate to the repository main page, then click Manage Repository → Edit Basic Information and add project tags to the "Tags" field.

I don't think the behavior of the fields is unclear and we haven't seen other users run into this particular difficulty.

Unfortunately, we can't help you with this problem. We didn't write this script, do not maintain it, and have never seen it before. You should try getting in touch with the script maintainers instead. We don't have the resources to provide support for third-party code.

That seems fine to me.