(D17404 is an earlier fix for a similar issue, but for self-auditors added via Herald.)

After 6 month seeing the bug, i think i've found why it does that.

To move forward, we need complete reproduction instructions which we can follow to reproduce this issue in a clean environment. See Contributing Bug Reports and Providing Reproduction Steps.

Do this man

Try as I might, I cannot reproduce this in a test instance hosted by yourselves.
The on screen description is the same (HEAD -> master), but the actual URL it goes to is different compared to my instance, even with the same repositories loaded.

@jaufrecht My pleasure. In general, using color gradients or shades is fine (and, actually, pretty much standard) for emphasizing trends. However, I would expect a use of gradients or shade of a single color to visualize a trend of a single category (topic, subject). In your case, though, the image presents trends in that fashion for multiple categories, which makes them difficult to distinguish and track. I would prefer and suggest using different colors for different categories and using a particular color's gradients or shades for each category across the time. Does it make sense to you?

I'm saying for you, not for me. Nevermind, I'm gathering that having verbal conversations isn't a priority for you guys and you don't see the value in it. No problem.

You already have all that in this public forum. We take feedback, feature requests, bug reports, have an open roadmap and design process - all for paying and non-paying customers.

@ablekh Thank you.

Allow me to clarify: as a product manager I've found it incredibly useful to talk to both current paying customers as well as prospective paying customers and users of existing free products to learn about their needs and things that work well and don't work well in the spirit of improving our products. I find that qualitative conversations like this can be very useful, sometimes more useful than quantitative and written communication.

I understand your suggestion, but taking feedback over phone is just like the worst ever for us given customers outnumber us 1,000,000 to 1 or so. It's not scalable which is why we ask people to participate here.

@jaufrecht Nice description. A quick comment on the attached image. Please take no offense, but IMHO, from the UX / usability perspective, this approach (using the same color's gradient or, in your case, shades) is pretty terrible and, as far as I know, is recommended against as the data visualization best practice. Hope this helps.

I'm not sure I understand. You want Phacility to spend development resources to understand your needs as a non-paying customer? As a thank-you?

@epriestley we're actually not, we're a SaaS users of Phabricator, self-hosted (dev.doctor.com). We are indeed free installs, but my gut is that our needs are no different than those SaaS folks that pay you. I'm offering my time as a form of thank you for what you've offered for free, though :) if you're interested in talk to large-scale customers and learning what their needs are (and even what they might pay for, as an example).

@Taskle, if you're a Phacility SAAS customer can you ping me at support@phacility.com with your instance name? I can't immediately find it. We're working to formalize the SAAS/prioritization relationship a little better, but we can push more weight behind requests if they're coming from paying customers vs free self-installs.

Here are some additional use cases and a sample implementation that is a Burn-up chart, not a Burndown chart, plus rationale.

Just wanted to chime in as a SaaS customer. :) We've been using Phab from a team of 15 to now we're about 100 people, and we use it for both our engineering teams as well as task management for our client services teams.

This also has SAAS customer interest.

In T11034#201013, @epriestley wrote:

If there's some remaining use case here, I'd also like to step back and understand it better since I suspect the best solution we can pursue is not any kind of UI change which makes it easier to find things by randomly typing guesses into the typeahead.

This got a mention in D17499, but when rendering a timeline we currently need two awards for each user who is going to get a full-sized profile image rendered.

Awesome (thanks for the super fast answer)!

My belief is that we've satisfied all the requirements for Translatewiki to move forward on their side.

Seeing the long list of merged commits here (thanks Evan and Nikerabbit for elaborating and explaining needs!), are there any further code changes in Phab needed before someone could set up a "Phabricator" project at http://translatewiki.net and let volunteers start contribute translations?

Resolved enough, unclear any benefit to installing to Favorites and Projects needs additional work to make it truly useful.

We have SAAS customer interest in this too, now.

Go to Conduit on your install.

Phrequent is a prototype application, and we don't provide support for these types of apps. Mostly it's expected that they will be incomplete and once we do move them to being officially supported they will have these features naturally (for example Conduit is "free" for any modern application.)

Is documentation available through other means than Conduit itself?

Phrequent is not installed on this server. Conduit only shows methods from installed applications.

Probably bump the version unconditionally now

(For example, if the goal was to very aggressively optimize for minimizing network traffic, we could read the entire repository history to figure out which refs were ancestors of other refs first? Then we could drop those and only ask for descendant refs. But this seems crazy, since it's saying that ~20 bytes of network traffic is more costly than like one hundred million disk I/O operations?)

it has to compare "What do I have" vs. "What do you have"

Do git ls-remote (which, curiously, seems to be significantly faster than git fetch even when git fetch is a no-op).

I think T12393 and this probably have a similar set of root causes.

Ah! That fixed it, thanks @epriestley. I'll let you know once I test out that configuration.

@epriestley I'm in the process of setting up phabricator to help mature the development workflow based on svn here, and make future transitions to git/perforce easier. Changelists would be a natural path here but the workaround for our use case is to just manually specify paths, but it's annoying if you have a locally modified file that you accidentally include in a diff, since you *have* to revert it to remove it from the diff. Using a changelist would let you avoid making the mistake in the first place.

Remarkup is cached, so you'll need to run bin/cache purge --purge-remarkup (or make an edit, or create a new post) to purge the cache.

@epriestley, I wouldn't mind testing that scenario out this weekend (I'll have to change a couple of domain name settings to create the scenario, but that's easily undone).

@stettberger: If there is anything missing from the WMF policy API extension, please feel free to file tasks under https://phabricator.wikimedia.org/tag/wikimedia_phabricator_extensions/ or open a differential revision against https://phabricator.wikimedia.org/source/phab-extensions/. I will be glad to review patches, I can't make any promises about feature requests but reasonable changes will be considered.

Brand new install on another VM, same Database server - same error. So can assume that the bug comes from data stored in database.

You can use any saved search query in Dashboards, the trick is you need to go build and save the query first. You don't construct it in Dashboards.

To define 6 pages yourself: use a text panel, then link to 6 pages in the text. For example, you might use text like this:

Ahh that did the trick - thanks.

The "Policy" task says "implement PolicyInterface", but the interface is already implemented so that Query works. The description should be adjusted to be more accurate.

Something that would be useful to us would be the ability to create, or probably better, assign a task, as it nears a due date. E.g. we may set up a task due in a year's time, and anticipate working on it two months before it is due. It would be great to be able to schedule the task to be assigned on a particular date, and perhaps moved on a workboard. I don't think this would need to be any more complicated than a Herald action that runs at a particular date/time rather than in response to some other action. I'm not familiar with what Calendar can already do, as we don't have prototype applications turned on for our install, so apologies if this is already possible. I just thought I would mention this use case here for future reference.

In T12372#215275, @epriestley wrote:

Great, thanks for testing it! We'll upstream that and I'll file something to put a longer-term fix in place.

"witter.com" <fakeemailtest+163@t>

ah yes this is my very favorite email address of all

Great, thanks for testing it! We'll upstream that and I'll file something to put a longer-term fix in place.