That's what I meant by embedded, yeah.

Is this panel in a panel?

In T8753#124642, @frankth wrote:

Can you help me ?

Can you help me ?

I would like to use this to keep my users updated about recent changes of our Phabricator instance.

We are using phabricator for reviews, repo hosting and task. The whole lot.

I think this is a race condition on building "default" file resources.

I've noticed it a few times as well. Always goes away after a refresh and may or may not happen after I've restarted php5-fpm.

Im curious if its something cache related, I think I normally notice this after restarting php5-fpm... not sure

Yea with a refresh it goes away.

I've seen it only once, and it immediately went away.

It was APC. Sorry. I thought I had restarted lighttpd after the pull but apparently I've lost my mind.

Is it possible that you didn't restart Apache (or PHP-FPM, if running nginx + php-fpm) and the old code is stuck in APC?

I'm up to date with your patch, Evan, but I'm still getting this error. I have a live repro if you want to see it.

We have this; I'm not sure if it's helpful or not (not much specifically about search filters):

@epriestley Do you have documentation in Diviner on custom queries? I had no idea that custom queries could be this flexible.

They have canUseInPanelContext() now so I think this got fixed somewhere.

I don't understand what this is asking for. You can build a panel which shows open tasks you are subscribed to like this:

T6560 is essentially the same issue, but specifically with tabbed panels.

T8034 is half of the "similar, less-severe" issue I mention above.

I think the original proposal was to make the panel disappear. This isn't something we'd be likely to implement, for the reasons @chad gave: it's super confusing and doesn't give users any tools to understand the behavior.

Or do both future engineer who may take on this task!

Pre-warning the dashboard creators still seems like the right way to solve the problem though.

Wasn't obvious to me that was your suggestion, I was only objecting to it vanishing.

oh.

@avivey that was my original proposal by I think @chad didn't like it.

We could also replace the [body of] the private panel with "You do not have permissions to view this panel". It would be easier to implement, and only slightly less useful.

Yeah I don't know how easy that is to figure out, but we should if we can.

Ah, I see. In that case, this task should morph to: inform the user, when in "management" mode that one of the panels may cause the whole dashboard to be unviewable.

That's pretty much my point. It's more confusing if things randomly disappear depending on the viewer, leads to confusion between admins, users, projects. We'd rather solve the core problem and have whole different dashboards which always work, than trying to have users keep track of who has access to what panel, when, where, and all the confusion that would lead to.

In this case you *do* have access (to the dashboard, and to all the other panels) to everything but a single panel. Just that one panel should disappear.

That's not a design pattern we follow, make stuff just disappear when you don't have access.

This may be related, but is a little more specific: right now adding a private panel to the dashboard makes the whole thing go private. IMHO it should render, but without the panel the user can't see.

Dashboards for certain users is T4103

I clicked on the "Authored" built-in

Oh, it's the "authored" prebuilt query specifically.

Does someone have detailed repro steps? Here's what I tried:

Sorry, those commit hashes are not correct. Issue seems to have been introduced in rPf64ca87bfea01a355f3fbf4fa03c460995b5da99

OK, I got a local install at HEAD and it's reproducing "Authored" as failing. Thanks for the report!

Issue doesn't seem to be present in rP3a2c2ae3c3ae3d88427ec96787840119508c2e73, and appears in rPb49645d25b60329cfdd181d7b1dd1dbce30d349f (and in HEAD)

Since an update yesterday

This breaks the built-in "Authored" and "All Tasks" queries.

We don't have plans to pursue this in the upstream, being able to make dashboard panels by column would likely solve most use cases here.

To define this a bit better, I'm imagining these components:

I updated my phabricator instance and this error no longer appears. Thanks @btrahan.

Thank you!

@btrahan - I saw your summary on D12227 - Clarifying that I do not have any Conpherences on the install which I saw the error.

I am seeing this error today, with phabricator on commit ba10e8ed41214a64be436e9bdbb9002a8dbba363.

Git pull fixed this...

Oh, I thought because the functionality exists for dashboards, it also exists for apps. Thanks for clarifying that.

That is this task.