I think I shipped this.

I've been busy with important emoji research.

Hows Nuance coming?

sorry maybe I am supposed to use these now 😱 😱 😱 😱

We un-install it on admin.phacility.com. :) :) :) :)

Hmm, we shouldn't allow Dashboards to be un-installed.

(The "Dashboard" item may also be affected.)

Ah this probably explains what I have observed on our installation too.

Yeah, some workarounds are:

I believe we see the same issue in our environment, but I didn't think much of it/rule out actual problems with our setup and just restarted the daemons the first few times it's happened.

I can no longer reproduce the edit issue at HEAD.

I papered over this in the short term by restarting daemons for all instances;

For mention purposes, see also T12618.

or vue

good time to learn react

It's a day of re-thinking the entire UI for me. I don't want to shoe-horn stuff in.

From blame, it looks like D15278 originally stuffed these and some other things into a bit of a weird place -- I think we had some other problems with too much stuff in dropdowns at the time, and that was sort of a "shove this stuff under a rug for now" change? But I don't really remember.

This is also extremely silly, but I sometimes do it because I'm dumb and have muscle-memory for ⌘+1+⇥+⌘+V+⏎: searching for an object URL doesn't jump you to that object URL, but you probably meant to put it in the other box.

Another user coincidentally ran into some questions here yesterday; I'm going to retarget this to take a stab a improving the documentation/description.

It doesn't look like Thunderbird can do this either. I did a "Body" "doesn't contain" "@Mattflaschen-WMF", and it just moves it anyway even if it is a ping (does have an @).

Totally my fault, I just didn't read half that sentence. 🐈

Thanks for looking into this so quickly.

And thanks for the report! Let us know if you run into anything else.

D17687 should dirty the cache properly on username changes. It should promote to stable within the next ~12 hours, and deploy to Phacility production about 24 hours from now.

I was able to resolve the issue by deleting my user's ssh key, and uploading the original ssh key material as a new Phabricator sshkey.

See also somewhat-related task T12397.