Mercurial > kallithea
view docs/usage/statistics.rst @ 4546:805ec49152c9
simplehg: don't quiet Hg output for push
I want to be able to see informational messages from e.g. the Hg Bugzilla
extension.
Here's output without the patch. This is identical to the output produced if
the Bugzilla extension is disabled:
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 1 changes to 1 files
remote: Repository size .hg:158.2 kB repo:0 B total:158.2 kB
remote: Last revision is now r324:6c03abbabb46
and with the patch:
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 1 changes to 1 files
remote: Repository size .hg:158.2 kB repo:0 B total:158.2 kB
remote: Last revision is now r324:6c03abbabb46
remote: bug 3270 already knows about changeset 6c03abbabb46
The last line indicates that the Bugzilla bug text already contains an entry
for that changeset. It's produced by a call to self.ui.status() in the
extension.
I think the point here is that the deleted code is ensuring that the remote hg
(i.e. the Kallithea hg) always runs with the --quiet flag when receiving a
push. This seems an arbitrary decision to me, and one that removes potentially
useful information from the output. I believe this behaviour is different to
that seen by the user if pushing to hgweb (I've not tried it, but inspected the
hgweb source for setting quiet) and is certainly different to pushing over ssh.
author | Jim Hague <jim.hague@acm.org> |
---|---|
date | Thu, 17 Jul 2014 12:47:56 +0100 |
parents | e73a69cb98dc |
children | 03bbd33bc084 |
line wrap: on
line source
.. _statistics: ========== Statistics ========== The Kallithea statistics system makes heavy demands of the server resources, so in order to keep a balance between usability and performance, the statistics are cached inside db and are gathered incrementally, this is how Kallithea does this: With Celery disabled -------------------- - On each first visit to the summary page a set of 250 commits are parsed and updates statistics cache. - This happens on each single visit to the statistics page until all commits are fetched. Statistics are kept cached until additional commits are added to the repository. In such a case Kallithea will only fetch the new commits when updating it's cache. With Celery enabled ------------------- - On the first visit to the summary page Kallithea will create tasks that will execute on celery workers. This task will gather all of the stats until all commits are parsed, each task will parse 250 commits, and run the next task to parse next 250 commits, until all of the commits are parsed. .. note:: At any time you can disable statistics on each repository via the repository edit form in the admin panel. To do this just uncheck the statistics checkbox.