The arcanist workflow is actually pretty awesome, but yes it's a bit of a switch if it's new to you. The Maniphest integration from reading the docs looks like it only works with Revisions, and not Commits. I don't think we've have plans to add it to Commits, though it's likely possible at some point (not much/any interest has been seen).

I am not using differential right now (but will be in the future. Just testing things one at a time right now). I was hoping the links could be added just from a revision committed in Diffusion. Are they only added if you use Differential?

Unfortunately no. Is there something I need to enable to add this functionality?

Oh, sorry, I think I'm misunderstanding you. These links are established during code review (Differential), not Audit. Are you using a pre-commit workflow (Arcanist)?

Yes, and nothing appears on T7 for you?

I have tried a few different methods, and tried to model if after example commits found in this Phabricator instance that look like they worked. Is this what you meant by putting it in the summary section?

@tgrosinger our handy guide is here: T5132: Document the special syntax you can use in commit messages to cause effects (Sounds like you're not putting them in the Summary?)

I am getting links from Diffusion to the task (in the commit message, the T123 will be a link), but the link is never showing up in Maniphest. Any suggestions for troubleshooting? I am using "Closes T123" as the second line in the commit message. I have also tried with "Maniphest Tasks" and "Fixes"

The same problem exists in git and I have the same issue over acceptability of my users who happen to be familiar with ReviewBoard.

Support Impact The remaining stuff is pretty hard to use.

Support Impact Substantial effect and unclear next steps.

Support Impact This has cropped up a number of times and is surprising and broken.

Presuming resolved.

Support Impact This is broken.

Closed by commit rP0ddb1875087b.

From what I can tell, the easiest way to resolve this is to increase innodb_buffer_pool_size. Generally, increasing innodb_buffer_pool_size is desirable anyway, because it will tend to improve performance overall.

Sorry, I can't reproduce this on this install or locally. Closing per https://secure.phabricator.com/book/phabricator/article/feedback/#unreproducible-problems

In T6208#77585, @epriestley wrote:

@hach-que is correct. We do not interact directly with Bugzilla, and do not have any plans to build integrations in the near term.

I got, THS.

@hach-que is correct. We do not interact directly with Bugzilla, and do not have any plans to build integrations in the near term.

As far as I can tell, all this feature does is cause bug IDs like "ABC-123" in a commit message to be turned into links. It's not integration with an external bug tracker.

Not reproducing here. When reproducing on our install, what happens is

Had some free time today and implemented this. The improvement however is not as big as i expected.
Doing a blame on phabricators __phutil_library_map__.php will take ~20sec without and ~15sec with the cache on my dev vm.

I'm sorry, I'm not able to reproduce this on this install. Does it reproduce here for you? Can you provide a list of steps to reproduce? What pygments are you running?

Yes, turning off Blame, the syntax highlighting works again immediately.

Do you have it pygments enabled/installed? https://secure.phabricator.com/book/phabricator/article/differential_faq/#how-can-i-enable-syntax

I can't reproduce this and it sounds like you can't either.

Today I updated phabricator with 212b0d2..8ebe9ce, and tried again and suddenly it is no longer reproducible…

@davisoa I've been running each revision of D8478 since I put it in. Admittedly with only internal use by three people but I haven't been noticing any issues.

The http://qa.in-portal.org/rSIM16064 should be http://qa.in-portal.org/rTSIM16064 in previous comment.

This continues to happen. For example:

If you have View in Editor functionality, then I suppose it worked at some point. I wonder how it was used knowing all problems that I've experienced with it.

We don't plan to support that.

You recommend that I create symlinks on my machine and name them like path in SVN repository? Won't it be easier to have per user setting, like editor url, where I specify from=>to replacements pairs to be applied to repository file path before giving it to %f in editor url.

You can use a path like /path/to/editor_symlinks/%r, then symlink working copies using callsigns.

Closed by commit rPHU6c29d5c8d169.

See T5031.

Also the comment textarea in Manifest doesn't clear when I hit Submit button.

Usually host goes till the first ? or if that's missing till the end of the string.

Specifically, this is a combination of parse_url() getting these URLs wrong, and then filtering we apply. Here's what parse_url() gets wrong:

Thanks Evan, the LockExtension has worked as desired for us using the fix suggested above. It would be great to have inbuilt support in the future for these.

I see.

We perform filtering after calling parse_url() to deal with cases it doesn't handle. This filtering gets these cases wrong.

Isn't parse_url function (http://php.net/manual/en/function.parse-url.php) used to parse url to determine protocol? I thought it handle that stuff without problems.

I think the underlying issue is with parsing URIs that don't have slashes in them. We assume the domain terminates with a slash, but idea://open?... does not. This causes us to incorrectly identify the URI protocol.

Probably somebody forgot to update language pack, when decision was made not to support more default editors :)

Haha, well that's news to me!

We're not interested in adding more protocols, which is why it's extendible.

We're not interested in adding more protocols, which is why it's extendible. But, we should obviously resolve this bugs!

Ok, I can reproduce that.

And original subject was to add the "idea" and "phpstorm" as allowed editor protocols as well.

Here is the link I've mentioned:

Yes, I did restarted the server. As I said I have 2 problems in one:

Ah, nevermind. I can't reproduce this, I'm able to set new values (using your examples), restart the server, and they appear as options. Did you restart your server? We should now tell you to restart when config values change, but that is a more recent feature, so your instance might not have it yet.

This line phpstorm://open?file=%f&line=%l as seen on screenshot I've originally attached to a task.

What specifically are you setting in your Display Preferences under "Editor"?

Nope, @hach-que. Your command gives following error:

I think it should maybe be:

Changing configuration allowed to save my new editor in Display Preferences. However when click on "Open in Editor" link in "View Options" a file on a commit page I get error dialog (url http://.../help/editorprotocol/):

I've managed to set new value from command line using this command:

./bin/config set uri.allowed-editor-protocols '{"http":true, "https":true, "txmt":true, "mvim":true, "vim":true, "subl":true, "emacs":true, "editor":true, "phpstorm":true, "idea":true}'

As advised I've tried to change configuration variable value, but got this error:

I had a hiccup finding this the other day so I'm going to do this.

In T6080#9, @chad wrote:

We also now crosslink object mentions, so it will get linked on the original commit in the timeline as well.

You also do not have put the > or any text specifically, we'll parse and link any commit hash.

Is your instance at HEAD? This is a very new feature.

But seems no crosslink in original commitment.

It sounds good. It can be also recognized in SVN commit message. but just title looks strange.

We also now crosslink object mentions, so it will get linked on the original commit in the timeline as well.