Yeah in those cases, writing your own "Internal Tools Status" application would probably be better.

A few things that might motivate writing an API panel (which pulls from external sources) instead:

(I agree that this is a bad solution for notifying users of downtime/maintenance on the current instance, and that rooster/broadcast is better.)

Maybe T8145 / T5231, but I think the driving use case there was "notify users of Phabricator downtime" specifically. I'm imagining the driving use cases here not affecting all users and not directly impacting Phabricator, just having wide enough impact that there's interest in surfacing them more broadly. e.g., "We're having a production incident affecting video upload, ops is investigating" is important, but not "every Phabricator user must be notified" important.

We also talked about a "Rooster" system as well. Something outside of dashboards that is tied to a time or is user-closable.

Doing a Phriction panel, an iframe panel, or a custom API panel would also be reasonable approaches.

I think we also have a "notify my users about event x or y or downtime" task floating around somewhere else.

Here's an example I could imagine us doing: we have some button on admin.phacility.com that says "Start a deploy". When that's pressed it causes these actions to occur:

My concern is users will install their own dashboards and this doesn't particularly solve anything. I don't know what the core problem is to suggest an alternative solution.

This one seems OKish to me -- I think those use cases are pretty reasonable and root-problem-ish? I'm assuming "waht's currently broken" and "can we do deploys" are information known by some other system or tool.

Please see Contributing Feature Requests

I'm going to merge this into T6018, which I think describes the same bug.

Since the same root problem you described was solved with adding the query icon and link, I'm going to close this out. Overall having this in it's own element lends to better discoverability, and solves the right problem vs. just hiding it in the header. Adding to both is possible, but falls under "Design Feedback" which we don't take as tasks on (see T10208).

It's a tab panel, not a query panel.

Oh, yes. I wonder why I did not notice this. Why doesn't the panel "Recent Tasks" on Dashboard 8 have a ?

We already provide a link in the form of the on Panels directly to the query.

It seems like this isn't reproducible in other environments. Feel free to file a new report if you are able to uncover more information in the future.

This is real dumb, but I think it only creates a moderate inconvenience so I probably won't try to dig into it until we do the next iteration on dashboards.

The link is to "RobH changed Tabs from codfw206eqiad207 to codfw206eqiad207esams208ulsfo209." specifically

What does "formatted in a strange way" mean? Nothing stands out as incorrect on the page you linked.

"RobH set Tabs to ." is also a bit weird

It sounds like no one can reproduce this problem anymore. If anyone runs into this again and can figure out reproduction steps, feel free to file a new task with details.

In this case...

Yes, I'd expect to do this:

What about the following solution:
Display the workboard to the user, if he is able to see it, but don't show the panels which he can't see?

The issue disappears today! I don't know why.

If you can see my upload gif , then it‘s ok !just{F1115848}

2 days is a very long time to import. I'd wait until it's finished (we should still fix the error if we can reproduce it)

Is the import complete?

In T10341#158952, @chad wrote:

Is this Subversion?

Is this Subversion?

Unfortunately we can't fix bugs we can't see (well, usually). If you have further details (like what type of repository) or errors in your Apache log, please post them.

Hi @chad , I added some info. I don't know the real reason honestly.

Please see Contributing Bug Reports. Specifically we can't take a bug report without you providing the reproduction steps. How can we reproduce this error?

I don't have any ideas on how to troubleshoot this, since it's most likely to be between the webserver and your browser and I've never run into it personally.

This is an amorphous, unfocused task and substantially resolved by profile menus and changes in HEAD or planned in connection with T10054, see also M1450.

pulled latest version still same

2015/12/06 20:28:44 [error] 7203#0: *9085 FastCGI sent in stderr: "[2015-12-06 19:28:43] EXCEPTION: (Exception) Construction of a DateTime() with epoch '1449419124.4675491878' raised an exception. at [<phabricator>/src/view/viewutils.php:86]
arcanist(head=master, ref.master=9e78d15fc0c7), phabricator(head=master, ref.master=5b4825cf1eea), phutil(head=master, ref.master=5538909d6468)

#0 <#2> phabricator_format_local_time(string, PhabricatorUser, string) called at [<phabricator>/src/view/viewutils.php:7]
#1 <#2> phabricator_date(string, PhabricatorUser) called at [<phabricator>/src/view/viewutils.php:20]
#2 <#2> phabricator_relative_date(string, PhabricatorUser) called at [<phabricator>/src/applications/feed/builder/PhabricatorFeedBuilder.php:46]
#3 <#2> PhabricatorFeedBuilder::buildView() called at [<phabricator>/src/applications/people/controller/PhabricatorPeopleProfileController.php:251]
#4 <#2> PhabricatorPeopleProfileController::buildPeopleFeed(PhabricatorUser, PhabricatorUser) called at [<phabricator>/src/applications/people/controller/PhabricatorPeopleProfileController.php:165]
#5 <#2> PhabricatorPeopleProfileController::processRequest() called at [<phabricator>/src/aphront/AphrontController.php:29]
#6 <#2> AphrontController::handleRequest(AphrontRequest) called at [<phabricator>/src/aphront/configuration/AphrontApplicationConfiguration.php:237]
#7 phlog(Exception) called at [<phabricator>/src/aphront/handler/PhabricatorDefaultRequestExceptionHandler.php:32]
#8 PhabricatorDefaultRequestExceptionHandler::handleRequestException(AphrontRequest, Exception) called at [<phabricator>/src/aphront/configuration/AphrontApplicationConfiguration.php:632]
#9 AphrontApplicationConfiguration::handleException(Exception) called at [<phabricator>/src/aphront/configuration/AphrontApplicationConfiguration.php:242]
#10 AphrontApplicationConfiguration::processRequest(AphrontRequest, PhutilDeferredLog, AphrontPHPHTTPSink, MultimeterControl) called at [<phabricator>/src/aphront/configuration/AphrontApplicati

I assume your install is at HEAD, correct?

There should be a stack trace in your web server logs. We're only interested in the root issue.

the error apears when function "phabricator_format_local_time" in phabricator/src/view/viewutils.php, gets a $epoch var that for some reason has a decimal point, so when some sort of activity somehow manages to get a timestamp from something like pushing a commit that has a decimal point, DateTime() will throw and exception, i don't know how phabricator manages to get that decimal point there, but i recently pushed a commit and it seems phabricator gave it a timestamp of "1449419124.4675491878", so anything that displays list of my activities (including my profile page) gets this error because of the invalid time stamp. i think there should be some code to make sure the timestamp is a rounded int.

See Contributing Bug Reports

i don't know how it happens, just sometimes it shows me that error, and some times it goes away

Please provide the steps to reproduce

i get the same thing

Yes, exactly that.

Specifically, you're talking about this?

As requested by Chad, an attempt to describe our use-case: