No problem -- we gave you a false start in Q528 and this behavior is pretty hard to guess at if you don't know the internals.

Specifically, this is the PHID you're looking for in the UI:

If you do this:

When you say "fail hard", you specifically mean that you get an exception message beginning with this text?

(Actually, I'm just going to respect the file policy but ignore policy failures.)

Here are more reliable reproduction steps:

I can't reproduce this. Here's what I did:

I'm going to attempt to reproduce this as written, but I will be shocked if these steps work to reproduce the issue you describe.

This search UI also needs to be updated:

My only (mild) concern with this is that object types may become slightly ambiguous in some contexts: currently, icons are (at least mostly) unique across object types. A tag icon or a briefcase icon is always a project. A calendar icon or a cocktail glass is always an event.

Does an administrator have two "Customize Menu..." links? Or does their link at the top also let them customize the global stuff?

I'm probably going to change this to repository and accept an ID, PHID, short name, or callsign, as all the Phabricator-side web/CLI stuff now does.

You can use bin/storage upgrade --apply phabricator:2016... to reapply a specific patch explicitly, even if it has previously been marked as applied. You can get the full names of patches from bin/storage status.

I expect our forking to be much lighter-weight than GitHub's (ideally, I'd like it to work something like git push whatever/branch creates a fork called "whatever"), forking is just a familiar metaphor.

I love it it is very good

Yeah, I don't particularly like "Global" (too technical) or "Favorites" (feels very Windows 98 to me: "My Documents", "My Computer" -- "Favorites" isn't as bad, but "My Thing" has always felt weirdly condescending to me).

• H140
• {H140}
• H141
• H141 force chad

everything will be OK :)

Relatively little doom appears to have befallen us.

This hasn't seen action in two years and a lot of the surrounding code has changed since then. If it's still an issue, please file a new bug report with reproduction steps demonstrating how to break an object so it doesn't index properly.

Maybe we can start with an "Add to homepage" action from Dashboards and see if we need the grouping/label? It gets tricky if you add two, we create a group, you reorganize one, you rename the label, you change your language, and you add another. Now we have to guess whether your "El Dashboardoes" label is a group of dashboards or not.

Or: if you aren't comfortable adding labels to a menu, you probably don't have an organizational role that requires you to pin 5 dashboards into subgroups on your homepage, and you can figure out how to customize it later when you need the increased power. Novice users can always use browser bookmarks or normal navigation, or administrators can add links to the global nav if there are actions that some users are consistently having difficulty with.

We can have an "add this page to the homepage menu" that just adds a link at the bottom of your custom stuff, and/or "Customize Menu" can take you to a modal choice between "add a link" and "do powerful things". But I think most users can handle it -- I don't recall too many issues with project profile menus, and when we removed them we got a fair amount of pushback so it sounds like the full-power version is getting use today.

Yeah. Default looks like this:

I think that's reasonable, but I'm not sure we even need to separate out dashboards -- if we do, it prevents me from putting them into functional sections I create with labels (like "Engineering").

(Or, if you're ambitious, you add 20 different links in 5 categories or whatever, and effectively replace the global menu with your own custom thing full of stuff.)

I think user links should go first, so they push all the global stuff down, out of the way. You add links for the 3-4 most important things, they show up at the top, and then presumably you aren't too concerned that admins occasionally shuffle the other stuff around since it's out of your way.

I'm not sure trying to auto-categorize is desirable because it means that stuff like create forms, wiki pages, etc., won't end up in the most logical place. It prevents me from creating an "Engineering" category for a company, or a "Getting Started" category for onboarding users on an open source install.

Seems to be working now. ¯\_(ツ)_/¯

For future reference, here's the sequence of problems I hit:

Your config looks very little like the config we recommend. Why are you using try_files instead of rewrite?

Can you show me:

GREAT NEWS! Times work again for me, personally.

This is pure scope creep, but I've always found Countdown anticlimactic when it reaches 0. I could imagine having this feature:

The intended target of the link is Cluster: Databases.

I can rename them, maybe MenuItem instead of Panel? I think when I wrote the stuff we had some more panel-like items in mind (like M1450) but haven't ended up building many of them, at least so far (cat facts and progress bar are the only non-item-like-ones, I think). Even if we do build richer stuff later I think MenuItem is reasonably clear.

One thought about binding them to dashboards is that users won't naturally be able to edit the menu anymore, to personalize it. But maybe we can put some kind of override mechanism on top of it.

I hope so!

That's expected if innodb_ft_max_token_size is not defined; specifically if this returns an error:

What is innodb_ft_min_token_size set to? The default is 3.