It sounds like this is resolved. We almost certainly can not raise a more specific exception.

I found problem, because I type fully LDAP DN (cn=root,dc=example,dc=domain) as Username at Import from LDAP.
but if there could have any error message will be better.

Which instructions did you follow that included a key called value_add? These instructions were wrong and should be updated.

Is there some other documentation we should fix that indicated those values were correct? If so we'll correct that. The Conduit app at least has the expected dictionary:

You're calling value_add instead of value on projects.add. It also must be sent as a list (array) and not a string.

• https://secure.phabricator.com/conduit/method/maniphest.edit/
  • insert in the field

[       {         "type": "title",         "value": "TEST_3"       },     {       "type": "description",       "value": "Test 3?"     },     {       "type": "owner",       "value": "PHID-USER-y7djwtvdkrc7sd2dymn6"     },     {       "type": "status",       "value": "open"     },     {       "type": "priority",       "value": "0"     },     {       "type": "projects.add",       "value_add": "PHID-PROJ-nitxwme6cvo45mcfry4s"      }   ]

Thanks, that helped.

Yes, this project has subproject.

You need to add members directly to subprojects. Parent projects are just the sums of all subproject members.

Is this a Parent Project you're trying to edit? That is, does the project has subprojects?

Can you show us a screenshot of the top section of the "Members" page for the project? It should look something like this:

i try do ./policy unlock PHID-PROJ-<hash>
all policy reset for all users but button "Add members" still inactive

I'm an admin

And what is your account?

./policy show PHID-PROJ-<hash>
OBJECT

What is the Join Policy of the project set to?

I want to add a new member

What specifically are you trying to do that needs fixing.

any ideas how i can fix this

Sorry i can't reproduce this bug now, but my phabricator regularly updated and we working in this project and the source of this bug may be earlier.

Bug reports must include reproduction steps. See Providing Reproduction Steps.

D15990 removes the Lamson instructions from the documentation.

After D15989, this dialog should properly include information about tree hash and commit hash matches. It could still be more clear, but appears to at least be working as intended now.

Basically, the metadata is sufficient to generate the "Local Commits" table and little else.

The commits are not in Diffusion. Here's a real example of the metadata we store for a commit:

Got it, thanks for taking the time to explain. When you say "metadata" for the commits, do you mean the commits are also in Diffusion (even if invisible)? If so, wouldn't this behavior affect Herald / Harbor Master?

When you run arc diff, you provide (explicitly or implicitly) a commit range. Phabricator stores:

The expected behavior is that when we discover a new commit, we search for any open revision which has an active diff with a commit that has the same commit hash or tree hash as one of the discovered commits. In this case, it appears that this revision did.

Prior to D15987, the easiest fix for this was to add --force:

Here and in one other report, revisions which are closed by matching a commit or tree hash with a discovered commit are not explaining this in "Explain Why". "Explain Why" is expected to be able to provide details about this:

Here are the commit hash and tree hash of the commit:

At present, the only way to get around the problem is to ignore arcanist and push directly to git for the change that involves this problem.

I am also facing same issue in a file. Can anyone suggest me the way to fix it?

Feel free to look at this information and anything else in the Hyper instance you need to.

Is it OK if I look at some of the data on your instance to diagnose this? I expect to look at this information:

Every task here has the latest progress / information already. There isn't a second task tracker, we develop in the open.

Hi @chad & @joshuaspence Any progress on this bug?

I can't reproduce this; I've used conduit to add the "Conduit" project to this task:

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?

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).

@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 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.

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.

• 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:

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

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