I am so sorry for the late reply, but I did not have the time to check up on this.
But yes, our Phabricator was out of date. I just did the update and now I do have that option!

Probably can try to install bc and report back if you still see it. What MySQL version are you running?

@avivey: 32bit, yes, no
and the error just went away...

Feed Story's getEpoch() is doing some serious magic: https://secure.phabricator.com/diffusion/P/browse/master/src/applications/feed/storage/PhabricatorFeedStoryData.php;20e6a4200dbc72760ea5de4eb15053bc1b2c8dac$41

Your welcome.

pulled latest version still same

Ok, I got it working. I'll add a tutorial style answer on another more suitable thread, and I am closing this for now.

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

Ok thanks a lot and sorry for the confusion! I shall start again from scratch, and post my findings here if I manage to run the phabricator's sshd on a custom port.

i get the same thing

So please follow the guide from start again, then i or someone lese will helps debugging the "normal" stuff failing like permission in sudo, or git-executables not in path.

On http://phabricator.example.com/config/group/diffusion/ theire is all stuff you wanna configure ! In peculiar the ssh-port, the ssh-user ect.

Thanks a lot for the elaborate reply! No, it doesn't throw any such error. I get straight shell access to my server.

Ah, oki. Was it not because comment are hidden field on new application form so if you can't edit the task, you can't edit the comment too.

because we have tooling which relies on the regular SSHD daemon being available on port 22. And thus, I have to add the remote like above.

From elsewhere:

Ok, sorry. I'll take a look at the support options. Thanks!

This does not describe a bug in Phabricator. See Support Resources and Contributing Bug Reports.

Custom linters for stuff like that are way to go, that's true: for example some projects may have very complicated naming scheme, where "files in views must be all lowercase with .template extension, placed into dirs corresponding to name of controller, every view should either correspond to action in said controller or be named "all" or stard with underscore [...]" 😉

Sorry didn't mean to tag this as "Bug Report", more like a "Question". Not sure how I can edit that :/

I just think this isn't very good:

In T9876#147243, @joshuaspence wrote:

For what it's worth, I think that this is a reasonable request. I think that the only way to implement this would be to use a custom message which would be specified in the .arclint file. For example:

.arclint

{
  "linters": {
    "file": {
      "type": "file",
      "file.regex": "(^[^\w]+$)",
      "file.message": "FIlename must consist only of punctuation characters, alphanumeric characters are forbidden."
    }
  }
}

For what it's worth, I think that this is a reasonable request. I think that the only way to implement this would be to use a custom message which would be specified in the .arclint file. For example:

probably just and android issue.

Yeah, just a mobile issue.

Nice.

I assume the use case for this is building tables in, e.g., Phriction documents with the status of various tasks.

@epriestley, if you braindump/document/discuss this elsewhere, leave a comment here. This is something I am interested in, as our startup is defining its culture, and we've had some growing pains that I feel our "core values" as documented have not be able to address in a meaningful way.

Apparently this is just how <textarea> works. Here's a test case in WebKit explicitly testing this behavior:

In T9908#147085, @epriestley wrote:

To clarify, it's critical to you that newbies not be able to, e.g., change the priorities of tasks they filed by making Conduit API calls?

I also made them work in Paste, so generalizing this task per D14416.

I implemented this a while ago:

This task doesn't describe a root problem. See Contributing Feature Requests for modern documentation on feature requests.

In any case, we can't reproduce this and aren't sure if it reproduces at HEAD. See Contributing Bug Reports.

See also D14665 for EditEngine integration, which slightly changes one call.

We haven't seen other requests for this and I think putting administrators in a project and using "Pusher's projects ..." is a pretty reasonable workaround. This can also now reasonably be written as an extension.

We haven't seen other requests for this in a year, and our behavior is technically correct and I think it is broadly reasonable.

I don't think this is a good fit for the upstream: it's inherently a bit unreliable, can't be made reliable, and I don't think the use case described here is a particularly robust one even if it's reasonable for some organizations.