Mercurial > kallithea
view docs/usage/troubleshooting.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 | a9a1560dad79 |
children | 03bbd33bc084 |
line wrap: on
line source
.. _troubleshooting: =============== Troubleshooting =============== :Q: **Missing static files?** :A: Make sure either to set the `static_files = true` in the .ini file or double check the root path for your http setup. It should point to for example: /home/my-virtual-python/lib/python2.7/site-packages/kallithea/public | :Q: **Can't install celery/rabbitmq?** :A: Don't worry Kallithea works without them too. No extra setup is required. Try out great celery docs for further help. | :Q: **Long lasting push timeouts?** :A: Make sure you set a longer timeouts in your proxy/fcgi settings, timeouts are caused by https server and not Kallithea. | :Q: **Large pushes timeouts?** :A: Make sure you set a proper max_body_size for the http server. Very often Apache, Nginx or other http servers kill the connection due to to large body. | :Q: **Apache doesn't pass basicAuth on pull/push?** :A: Make sure you added `WSGIPassAuthorization true`. | :Q: **Git fails on push/pull?** :A: Make sure you're using an wsgi http server that can handle chunked encoding such as `waitress` or `gunicorn` | :Q: **How i use hooks in Kallithea?** :A: It's easy if they are python hooks just use advanced link in hooks section in Admin panel, that works only for Mercurial. If you want to use githooks, just install proper one in repository eg. create file in `/gitrepo/hooks/pre-receive`. You can also use Kallithea-extensions to connect to callback hooks, for both Git and Mercurial. | :Q: **Kallithea is slow for me, how can i make it faster?** :A: See the :ref:`performance` section | :Q: **UnicodeDecodeError on Apache mod_wsgi** :A: Please read: https://docs.djangoproject.com/en/dev/howto/deployment/wsgi/modwsgi/#if-you-get-a-unicodeencodeerror | :Q: **Requests hanging on Windows** :A: Please try out with disabled Antivirus software, there are some known problems with Eset Anitivirus. Make sure you have installed latest windows patches (especially KB2789397) .. _virtualenv: http://pypi.python.org/pypi/virtualenv .. _python: http://www.python.org/ .. _mercurial: http://mercurial.selenic.com/ .. _celery: http://celeryproject.org/ .. _rabbitmq: http://www.rabbitmq.com/ .. _python-ldap: http://www.python-ldap.org/ .. _mercurial-server: http://www.lshift.net/mercurial-server.html .. _PublishingRepositories: http://mercurial.selenic.com/wiki/PublishingRepositories .. _Issues tracker: https://bitbucket.org/conservancy/kallithea/issues