This isn't a bug. Diff properties are not intended to be an arbitrary key-value datastore for API consumers.

This field is only populated when you update a revision, and always contains the first line of the update message, which is also posted as a comment.

This hasn't moved forward in a year so I'm just going to close it. We've removed header text in the latest UI iteration, too, and I imagine the button will be replaced completely with universal send-on-enter before long.

When this is in stable and we upgrade I will have a reminder to keep an eye on logs and come back here

Although it's still a little early to be sure, we appear to have fixed the policy issue with unit test failures (D17029). Not sure if that actually impacted this or not.

My dashboard changed at some point and no one else seems to care, so let's wait for this to be more than an @epriestley-problem.

D17037 should fix the documentation, it definitely wasn't very clear as written. That should land some time today and the docs should be updated in about 24 hours.

Omg. I feel so stupid now. In the guide I read, that should be interpreted as 8MB, but I guess it wasn't... Works fine now, thanks a bunch!
This can be closed..

In the first row of that table, it appears that you have configured a storage.mysql-engine.max-size of 8 ("8 bytes"). Try using 8388608 ("8 megabytes") instead?

If you want to come up with a specific list of domains I'm happy to buy them, but there are many hundreds of domains which differ from phacility.com by only one keystroke and buying hundreds of domains isn't cheap in terms of the amount of work I have to do to do it.

Sure, here goes:

I can find this task by searching for "あああああ" so the CJK stuff may not really be much of an issue anymore? Maybe just an issue with Chinese because the index doesn't know how to tokenize words?

At least today, our error rate on this seems so low that it probably isn't worth implementing. We could take another look at it if we see more of it in the future (perhaps after we begin encouraging application development), but we haven't seen more of this that I can recall recently.

Paste now shows "Old", "New" and "Diff", so you can copy/paste from "Old" to revert. Not perfect, but I think this arises relatively rarely. See T11881 for a followup.

This is extremely old and it's not clear to me which bad cases remain -- I can't immediately find any by fiddling. If any do remain, they haven't turned up again in about two years. If you're still seeing issues, feel free to file a new task with a modern test case.

No worries, totally understandable.

This picked up a few options through engine support and T11957 is adding some more. Particularly, default view is now "Authored" which I think resolves the original issue. I think the more-root problem is "Dashboards are kind of weird with all the panel copying", which is something we're aware of.

I am very sorry I am declaring t-shirt bankruptcy because I have learned it takes me over five hundred years to ship a t-shirt.

At some point after we get this working for Home, I want to replace the "Quick Create" menu with a similar customizable profile menu, resolving T5867.

rCORE9d89c996844c4599afc1cec9454a71dd80a69c6c threw out the -o pipefail nonsense in CoreHostBackupWorkflow.

(I renamed the "Up for Grabs" column to "Ready", and kicked this out since it doesn't have detailed technical instructions that a new contributor could follow like the other tasks in that column do.)

Can you browse to https://your.install.com/applications/view/PhabricatorFilesApplication/ and post a screenshot of the "Storage Engines" panel on that page? It should look a little bit like this (example from this install), although your settings are presumably different:

In general, please follow Contributing Feature Requests when filing feature requests. We have no plans to expand on tokens beyond T11217. They are a lighthearted and frivolous application. I'd recommend un-installing it if it is causing user confusion (you wouldn't be the first install to do so).

As I noted in T11217, this isn't exactly a duplicate. Tokens today are created with a class (tokens-coin-2 above) in their <span>. I don't see why title="Piece of Eight" couldn't also be added to that tag.

T12000 isn't really a duplicate. It's more of an enhancement for today's tokens. Of course, it'd be useful for this eventually, too, but that's tangential.

Token added for effect. ;)

This doesn't seem to be going anywhere too fast so I'm just going to nuke it while I'm combing through old things rather than letting it collect dust forever.