Here's a super helpful photo of my screen :3 :3 :3 :3

Yeah, I'm using a Dell U3011.

I don't know how to reproduce this, either. This may fix itself as T9132 evolves.

Here's what's happening, in detail:

This seems straightforward to reproduce:

Drydock is also a prototype, see User Guide: Prototype Applications.

You are about 4 months out of date.

Cool, let us know if you run into trouble. I think it should be pretty easy to port any existing code which does generally transaction-like things, but might have missed something.

My initial thought is that we should maybe just parse strings in various "almost certainly time" formats -- rather than adding a special syntax -- like:

D14575 passes transactions to HeraldAdapters, so custom HeraldActions may examine them. The action will receive concrete, persisted transactions which have been validated, merged, checked, and applied. This will land shortly.

Problems with these events which you are exposed to:

Primarily, it only fires some of the time, per this task.

Fixed in HEAD (D14571).

Haha, no problem. Definitely not a big deal either way.

Ah, okay, I wasn't sure if "cool!" meant "approved" or "I'll look into it".

I can give you an extension for this in about 15 minutes (at consulting rates).

You can't currently examine the most-recently-applied set of transactions, although we could reasonably pass them down and expose them.

I'd like to remove this event, because (a) it doesn't work right and never has and (b) all use cases we've seen are better suited to either Herald or mechanisms covered in T5462.

Can you do that with Herald instead?

What does the logic in your listener do?

Thanks! Should be fixed in HEAD.

Yeah, I'd really like to just get rid of this option. It's definitely not something we'd accept upstream today.

We haven't seen other installs encounter difficulty here. T5055 will eventually build some flavor of first-party package manager which should address a large superset of this problem class.

D14523 possibly describes a cleaner fix for this (special case autoloads when class_exists() is on the stack).

Who does the transcript show as the "Reviewer" for the change?

This is intentional, consistent, documented, etc.

No one else can reproduce this. storage upgrade --trace ... might provide some insight, or add --xprofile to that or whatever. We can look at it in more detail if you can narrow it down more.

This report doesn't appear to describe a specific problem.

It's intentional that we normalize the slugs to try to make typing URLs a little more forgiving: For example, if you go to any of these links:

Just to set expectations:

There were some changes to slugs about 6 weeks ago (D14260, D14261, D14287) but I don't think they would have affected this.

Since we can't reproduce this, I'm not sure how we could fix it.

This task doesn't contain enough information for us to reproduce the problem you're encountering. Please see Contributing Bug Reports for an outline of what we need in an actionable bug report.

I have made these changes to the planning document which are hopefully more clear:

Just to confirm, there are no plans to implement this within some timeframe, right?

That isn't what the planning document is intended to convey. I'll update it to make it more clear.

I've been using the ((alias)) syntax pretty frequently and it's been really helpful -- we have a bunch of documentation we point people at all the time, and before Phurl I'd open a new tab, search for the document, copy-paste the URL, and maybe put some [[ ... | nice title ]] syntax around it. Now I just ((thing)) and it's way easier. The search + copy/paste workflow wasn't hugely time consuming, but it was really annoying.

Phurl (T6049) is still a prototype and not yet documented.

@polybuildr, please see Planning.

This Phabricator install is not related to Wikipedia.

We don't plan to support these webhooks.

Cool. We definitely want to make dashboards easier to use in the future, but it's entangled with a bunch of "Welcome" / "Role Profiles" / "New User Experience" stuff that makes it a big project. Maaaaaaaaaybe Q1 2016-ish-ish. Maybe?

Just to make sure I remember things, specific issue is:

Alternatively, you could use a dashboard to provide the "executive dashboard" view, and bring text into that with text panels: