It looks like the original user may have just wanted (or been satisfied with) a Diffusion file-line link anyway? Thread is sort of ambiguous:

We could change the URL as a side effect of starting an inline comment, although you'd have to cancel the inline comment afterward.

Looks like we could do what we do in Diffusion already, just change the URL, no interaction needed inline?

This is fairly involved in the general case:

D16001 likely provides an appropriate general-purpose mechanism for the user cache pool.

Roughly, I think T10333, T5474, and T4863 are leading the way to making boards more magical and PM friendly. I would want to continue on and build those first and see if most of what you want could already be accomplished with those features. Since this request is mostly hypothetical, I'm going to close it out for now and we can revisit things down the road.

Actually it's kind of the same issue with Calendar. When creating an event it would really be nice to be able to specify the time zone of the event, when the time zone of the event differs from the time zone of the browser.

Mystery Query: Where is this coming from?

Summarizing caching for my own benefit. See also T10078, T10077.

We have all the information we need, I don't have suggestions for workarounds. This isn't on any immediate roadmap. See Planning for how we prioritize requests.

@chad Just want to follow up, does my latest comment explain my use case? is there any recommended workaround or future change that could help me with that?

What is the problem you are specifically trying to solve with using Countdown vs. Calendar? We have plans to greatly improve Calendar, but Countdown is not something we'll likely ever prioritize for new features.

Additional clarification. This happens if you give Arcanist an absolute path when doing an arc diff call.

Thanks for your answer!
I see your point. I have to update git to a newer version. I will let you know if it worked.

Thanks! Seems to work!

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

We may pursue this eventually but there are hundreds of hours of work between where we are today and scalable, no-code-required bot support.

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.

That's all there is right now. T10363, T5462 are probably most relevant, but there isn't a short, quick path to what you likely want.

Is there a doc somewhere on how to configure this for Slack though? Can it post only Diffusion updates or does it have to post everything? If the latter, that's going to be way to noisy and won't work I'm afraid.

Ah, I didn't know you had to edit it at https://admin.phacility.com/. I was looking at the instance config app.

Are you on http://admin.phacility.com or your local instance?

I don't think I can change this setting: "Configuration Locked". Can you guys do it for us?

http-feed-hooks in your Phacility instance config can push events to Slack. It's basic, but should work today.

I haven't actually looked into it yet, but https://github.com/etcinit/phabulous might support this out-of-the-box (Although their instructions site has lost its SSL at the moment),

Yeah, that's how git normally works; Phabricator does git push from the Phab copy up to the mirror (Because it's expected that users will git clone from the mirror). There's a git feature to allow git push to have a workspace and update it - search https://git-scm.com/docs/git-config for updateInstead to see it. I think it's intended for your exact use-case, but you should read about it.

Here's an example that blocks everything except some whitelist rules:

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

Please stop testing your application against our server. This is a working installation. You can spin up a test instance at http://phacility.com if you do not have the ability to install and test Phabricator locally.

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 avivey for your answer! Do you have by chance an example?

Phabricator can mirror a repository to a specified location - see Diffusion URIs guide - essentially, replacing this specific hook (You still need to configure it for each repository).

Observed repositories should now version in a reasonable way.

I'm surprised we don't spawn a dialog here, so we'll clear that up. Thanks for the report!