You destroyed the original file in Files too, right?

No problem, we're not in any rush.

You should be able to implement canAddToObject() to do this. If you want a Home-only item, implement it like this:

I'm going to fix this Real Soon, I absolutely Definitely Promise 100% ™ ®. But I'll accept a patch from a reputable contributor like @jcox any day.

Can haz badge??? 🍺

I don't believe this is related to E being set in variables_order.

Generally makes sense to me.

Per T12218, the Phacility cluster is reaching a scale (~50 devices) where we need to improve tooling over "open a bunch of terminal windows". I want to look at implementing Phage for this use case and see how far I can get.

Yeah, same here. Both videos are of similar size (1.6MB vs 2.1MB) and both appear to legitimately be MP4 / H264 videos (neither is some kind of obviously spooky magic like an AVI named .mp4).

Here's what I see in Chrome at time of writing:

(Maybe the real user report was something only indirectly related, like putting the query on a Dashboard? That would make sense given that the name talks about dashboards...)

I think it should use the same global/personal paradigm (let administrators save Global queries, supplementing the current ability for users to save personal queries).

We queried a subset of instances for the date of the most recent session activity, to estimate the impact of requiring free instances to log in periodically to remain active:

I think I'm just going to remove the "profile picture" text from the description to resolve this. The account.editable option is very old and I'd eventually like to remove it, but making the description more clear is an easier fix for now.

Thanks! I believe I broke this in D15165, a little more than a year ago.

With text-overflow: ellipsis; and no truncation:

See this document for instructions on getting Phacility support:

(Or whatever more nuanced version of things you want to do. But that's the current fate/rationale of phabricator-home.)

.phabricator-home makes the menu full-screen on mobile, so it's currently only applied to /.

ayep

From the home page, you can uninstall Home like this:

Put this workflow inside "Edit Menu"

Two possible alternatives to crumbs I can come up with, although I don't love either:

One other thought: it might be nice to provide a way to get to the dashboard from the dashboard-in-a-menu view. Currently, there's no way to "Edit This Dashboard" from Home or Projects: you have to go to Dashboards, hunt it down, and then manage things from there.

Sounds good, let us know if you come up with repro steps.

This is now available in the Phacility cluster. It appeared to work correctly on a test instance:

The spooky emoji and icons are real lackluster, barely a respectable spook in the lot: 👻 💀 ☠ 🍖

D17311 makes this stop fataling, but you're stuck with the panel for now. This should get fixed soon, but I don't want to try to sneak anything more ambitious in before the release cut.

tyvm 🙏

Was the sequence of actions like this:

I can't reproduce this: removing panels from dashboards works fine for me:

"Bizarro Gremlin" is just an alias for Quicksand

🙉

I think we currently don't really try to handle these cases:

That tip probably does not fit on screen in any of the orientations: it obviously won't fit to the north or east. If we try to put it to the south, part of it will be offscreen to the right. If we try to put it to the west, part of it will be off the top of the screen (the rectangle we use to detect the size of the tip box is slightly larger than the actual pixel size of the tip because we get weird scrollbar interactions if we use the size of the tip exactly).

My trick is:

Here's what I see:

Yeah, I don't think I fixed it. I tried this set of steps at master prior to D17308:

I'm not sure if I actually fixed @rphl's issue or not. D17308 was just aimed at the existing issue under the theory that we'll see more of it after this ships if we aren't already seeing it, but his report definitely might be a new issue.

This should now be resolved at HEAD of master, and should promote to stable later today.

Thanks! I think this is the timeline of events:

Per above, it sounds like upgrading fixed what you were seeing?

This isn't a bug report we can accept upstream. See Contributing Bug Reports for help. In particular:

Does that explain what you're seeing locally?