Page MenuHomePhabricator

Recent activity displays several commits in the loop
Closed, DuplicatePublic

Description

Hello,
Recently I added new repository to phabricator. Then I commited a local git repo (from etckeeper) to phabricator repo. Since then recent activity displays all the time those commits in a loop with current date. Check this screenshot:


I'm using 1120c465e480f503686ab503e2cf1e1f1b6cf16d commit of phabricator.

Event Timeline

skibbipl raised the priority of this task from to Needs Triage.
skibbipl updated the task description. (Show Details)
skibbipl added a subscriber: skibbipl.
btrahan added a subscriber: btrahan.

See T6350. It is helpful if you can run

bin/phd log

and see if you have any different / new stack traces. Note as well T1191 in case these commits have character set problems.

skibbipl added a comment.EditedOct 27 2014, 5:37 PM

Yeah, something really went wrong with this repository:

Daemon 301 STDE [Mon, 20 Oct 2014 20:47:37 +0200] [2014-10-20 20:47:36] EXCEPTION: (PhutilProxyException) Error while updating the "rSVRCFG" repository. {>} (CommandException) Command failed with error #255!
Daemon 301 STDE [Mon, 20 Oct 2014 20:47:37 +0200] COMMAND
Daemon 301 STDE [Mon, 20 Oct 2014 20:47:37 +0200] '/opt/phabricator/bin/repository' update  -- 'SVRCFG'
Daemon 301 STDE [Mon, 20 Oct 2014 20:47:37 +0200]
Daemon 301 STDE [Mon, 20 Oct 2014 20:47:37 +0200] STDOUT
Daemon 301 STDE [Mon, 20 Oct 2014 20:47:37 +0200] (empty)
Daemon 301 STDE [Mon, 20 Oct 2014 20:47:37 +0200]
Daemon 301 STDE [Mon, 20 Oct 2014 20:47:37 +0200] STDERR
Daemon 301 STDE [Mon, 20 Oct 2014 20:47:37 +0200] [2014-10-20 20:47:36] EXCEPTION: (PhutilLockException) global:phabricator:PhabricatorRepositoryManagementUpdateWorkflow:SVRCFG at [<phabricator>/src/infrastructure/util/PhabricatorGlobalLock.php:94]
Daemon 301 STDE [Mon, 20 Oct 2014 20:47:37 +0200]   #0 PhabricatorGlobalLock::doLock(double) called at [<phutil>/src/filesystem/PhutilLock.php:167]
Daemon 301 STDE [Mon, 20 Oct 2014 20:47:37 +0200]   #1 PhutilLock::lock() called at [<phabricator>/src/applications/repository/management/PhabricatorRepositoryManagementUpdateWorkflow.php:74]
Daemon 301 STDE [Mon, 20 Oct 2014 20:47:37 +0200]   #2 PhabricatorRepositoryManagementUpdateWorkflow::execute(PhutilArgumentParser) called at [<phutil>/src/parser/argument/PhutilArgumentParser.php:394]
Daemon 301 STDE [Mon, 20 Oct 2014 20:47:37 +0200]   #3 PhutilArgumentParser::parseWorkflowsFull(array) called at [<phutil>/src/parser/argument/PhutilArgumentParser.php:290]
Daemon 301 STDE [Mon, 20 Oct 2014 20:47:37 +0200]   #4 PhutilArgumentParser::parseWorkflows(array) called at [<phabricator>/scripts/repository/manage_repositories.php:22]
Daemon 301 STDE [Mon, 20 Oct 2014 20:47:37 +0200]  at [<phutil>/src/future/exec/ExecFuture.php:397]
Daemon 301 STDE [Mon, 20 Oct 2014 20:47:37 +0200]   #0 phlog(PhutilProxyException) called at [<phabricator>/src/applications/repository/daemon/PhabricatorRepositoryPullLocalDaemon.php:335]
Daemon 301 STDE [Mon, 20 Oct 2014 20:47:37 +0200]   #1 PhabricatorRepositoryPullLocalDaemon::resolveUpdateFuture(PhabricatorRepository, ExecFuture, integer) called at [<phabricator>/src/applications/repository/daemon/PhabricatorRepositoryPullLocalDaemon.php:198]
Daemon 301 STDE [Mon, 20 Oct 2014 20:47:37 +0200]   #2 PhabricatorRepositoryPullLocalDaemon::run() called at [<phutil>/src/daemon/PhutilDaemon.php:91]
Daemon 301 STDE [Mon, 20 Oct 2014 20:47:37 +0200]   #3 PhutilDaemon::execute() called at [<phutil>/scripts/daemon/exec/exec_daemon.php:111]

Anyway I've deleted this repository and recent activity seems to work fine. But feed database has over 10000 records which is way too much, we don't use phabricator that much.
BTW: I created that faulty repository in phabricator, which was pulled on 19/10/2014.