Caches should be purged, let me know if you're still seeing issues? D15311 will fix the underlying problem, and should promote and deploy in the next 24 hours.

This is also a problem in my environment - jpegPhoto populates correctly for other applications but not Phabricator

This is a highly valuable feature for my use case as well

Great, thanks @epriestley!

¯\_(ツ)_/¯ @epriestley

I'll clear the caches on your install and disassociate the {icon} rule from the Macro app. I think the original idea was that {icon} is silly nonsense like Macro, but {icon} has proven to be both silly nonsense and a super serious useful business tool.

The icon syntax probably started as a "fun" feature, which would make sense to dump in Macro...

The existing thing issue is caching issue - for privately hosted installs I'd say "clear the caches", but you can'd do that on phacility (Needs db access).

Is this the only case of remarkup syntax that is tied to having an app enabled? This should really be documented in https://secure.phabricator.com/book/phabricator/article/remarkup/.

Yeah, I don't think it used to be like this ~1 year ago.

This came up in IRC a week or two ago, so I've looked.
It was always there.

Weird, whyyyyyyyyyyyyyyyyyyyyyyy.

the {icon foo} syntax is part of the Macro app, so it's disabled.

Our instance is "hyper" BTW if this helps.

Yes, Macro is uninstalled.

Did you disable the "Macro" app?

Can you be more specific than just Phacility? I can't reproduce this offhand anywhere.

Is this the exact remote URL? https://github.com/JSkill/iOS-App.git
If it's private repo, what should I put to credential screen?

Thanks for help!

This is via discussion on IRC, but the request captures it pretty well.

@hyOzd No, this utilizes KaTeX and renders LaTeX using HTML and CSS. It is completely combined into the normal rendering workflow and is cached properly.

@ProfFan does this create images on the server side?

I think this issue was fixed by 58c2141 (Feb 16) which hasn't promoted to stable yet. You can either upgrade to master now, or it should promote to stable in about 24 hours. If you want, you can subscribe to the Changelog to keep track of when we promote.

Yes, the affected repositories are mercurial, there are several. The version is the latest stable one (https://secure.phabricator.com/w/changelog/2016.07/). I have not yet found a way to reproduce this behavior nor can I tell what the affected repositories have in common (not all are affected).

Just to confirm, this is a Mercurial repository, right? (I'm assuming it is because of default instead of master, but just want to make sure.)

Please fill out a full bug report, including your version and steps to reproduce. See Contributing Bug Reports.

I did a rough implementation of this functionality (full of dirty hacks) here at GitHub.

Some browsers (Safari, at least) also take several seconds (well, two seconds?) to render title attributes after a hover, which reduces their value as a way to quickly get more information -- I can click the "Edit" icon and find the information more quickly than Safari pops up the title text.

You're right. I think it's the best alternative while there's no pop-up. We'll go with this option, because using milestones that way can become a problem in the future.

In T10349#160305, @cburroughs wrote:

A task tagged with a sub-project, is still in the parent project, right? So it hasn't been "removed" from Dashboards

There's no space to show that columns in cards, but would it be possible to show them in a tooltip?

After observing the feature on this install I feel like the email messages are misleading, or I'm confused about how sub-projects work.

I think it's vanishingly unlikely that we'll write a visual DAG editor.

In general, we can't possibly create buttons for everything -- there are way too many rules, and some of the rules don't lend themselves easily to clicking a button. The icon already links to the full documentation, which explains everything (and this document is huge, because there are ton of rules).

It sounds like no one can reproduce this problem anymore. If anyone runs into this again and can figure out reproduction steps, feel free to file a new task with details.

In this case...

There's some context and discussion in T4207. Briefly, task dependencies are currently a directed acyclic graph, not a tree, and DAGs don't lend themselves well to visualization or drag-and-drop editing.

It has been greatly improved.

sorry i might have let the interns play with the board for marketing purposes

Oh, never mind, I figured it out. :3

I think this issue was fixed by 58c2141 (Feb 16), which is a little ahead of where you are. You can update to master to pick it up right away, or it should be available in stable in about 24 hours (if you want, you can subscribe to the Changelog page to keep an eye on when we promote to stable).

phabricator

70c679110e1d4632d19ca160379f83f6f20d79d1 (Sat, Feb 13)

arcanist

ed476cf8489c4bf41b7a0075f15d40820d640fe4 (Sat, Feb 13)

phutil

9c472e7c9b64395424c6cd25734bf239cb3c113d (Sat, Jan 23)

Can you either confirm that you're running HEAD of master, or tell me what version of Phabricator are you currently running?

Our projects make heavy use of mercurial tags too, for version tagging and it would be great to see them in Phabricator to easily compare files between versions (they're way more easy to remember than changeset hashes).

Yes, I'd expect to do this:

What about the following solution:
Display the workboard to the user, if he is able to see it, but don't show the panels which he can't see?

Sorry -- I'm happy to walk you through the technical details in greater depth at consulting rates (see Consulting) but want to draw a hard line that "not supported" really means "not supported" on this.

@epriestley Thanks for the prompt answer. Isn't there any way to mark these preview files as temporary, or any maintenance task that I could run to remove all graphviz.png files that are not referenced from anywhere?

@chad Was that just testing something, or a vote for this as a substantial problem?

@thuffir, I can't come up with an easy fix for that.

I got this:

I got the same problem with HEAD of master.
it seems relate to clone a git repo with gziped post data by http.

@epriestley It would be funny to read that book :)

There is a problem I have stumbled upon.