BTW why I was not able to assign any labels to issue? Strange...

Running at least PHP 5.3.6? That's when getExtension() was added to DirectoryIterator.

Oh... My host has 5.3.3, it is on CentOS and they do not change versions... Sad :( May be will try to install 5.4 there as second version, but it is another story. Closing :) Thanks!

Installed PHP 5.4 :) Now I have another error:

DomainException

Requires authentication
In: /home/***/vendor/joomla/framework/src/Joomla/Github/GithubObject.php@118

Can you post the full stack trace for this?

File Line Class->Method()
Users.php 57 Joomla\Github\GithubObject->processResponse()
LoginController.php 105 Joomla\Github\Package\Users->getAuthenticatedUser()
TrackerApplication.php 339 Joomla\Tracker\Components\Users\Controller\LoginController->execute()
TrackerApplication.php 165 Joomla\Tracker\Application\TrackerApplication->executeComponent()
AbstractWebApplication.php 127 Joomla\Tracker\Application\TrackerApplication->doExecute()
index.php 31 Joomla\Application\AbstractWebApplication->execute()

On http://issues.joomla.org/project/jtracker/stats getting the same DomainException, but only when logged in. @elkuku any ideas?

I'm logged in and I'm not getting the error.

Weird, I'm not getting it now.

The stats view does not require authentication (does not use it) - did you really get the "Requires authentication" message ?

Could it be that we are again using the fishy J stream wrapper ?... will investigate.. in the meantime... let's blame GitHub ;)

Could you check again please ;)

OK I got the above mentioned DomainException (without any message) on http://issues.joomla.org/project/jtracker/stats while not being logged in - sometimes, and sometimes not - so it's definitely our main service provider's fault :(

It works now on http://issues.joomla.org/. Will check it later today on my host. Currently doing my primary office job :)

Still I have the same error :( May be it is hosting related?

BTW I did not have it on the some-new-staff branch. Seems like fixed (or probably not our code fault)?

so, what's the status on this ? ;)

I think that fixed.