Re: Issue #161: No such table error with celery (conservancy/kallithea)

2015-10-09 Thread Dominik Ruf
It seems to me that celery is not using the same db as kallithea.
How do you start celery?
Are you using the same .ini file for celery and kallithea?

cheers
Dominik

___
kallithea-general mailing list
kallithea-general@sfconservancy.org
http://lists.sfconservancy.org/mailman/listinfo/kallithea-general


Status update: CPython, Kallithea, & GitLab

2015-10-09 Thread Nick Coghlan
Hi folks,

Some time back I posted here regarding CPython's evaluation of our
options for repository hosting:
http://lists.sfconservancy.org/pipermail/kallithea-general/2014q4/60.html

Originally, this was a comparison between my proposal for a Kallithea
based solution, and an alternative proposal for a GitHub+Phabricator
based solution.

More recently however, Barry Warsaw suggested GitLab as a commercially
supported open source option:
https://www.python.org/dev/peps/pep-0507/

I think Barry's proposal is a better fit for our needs than a
self-supported Kallithea based solution, so I wanted to let the
Kallithea community know directly that I've withdrawn my Kallithea
based proposals:
https://mail.python.org/pipermail/core-workflow/2015-October/000227.html

Thanks for all your work on Kallithea folks, and sorry I wasn't able
to find the necessary time to help grow your community!

Regards,
Nick.

-- 
Nick Coghlan   |   ncogh...@gmail.com   |   Brisbane, Australia
___
kallithea-general mailing list
kallithea-general@sfconservancy.org
http://lists.sfconservancy.org/mailman/listinfo/kallithea-general


Issue #165: Interval sync/update for "remote repositories" (conservancy/kallithea)

2015-10-09 Thread André Klitzing
New issue 165: Interval sync/update for "remote repositories"
https://bitbucket.org/conservancy/kallithea/issues/165/interval-sync-update-for-remote

André Klitzing:

Hi!

I like to request a feature to set an interval to automatically sync a remote 
repository. We have some repositories that were cloned with the "remote 
repository"-feature. As we use this as an internal read-only mirror we like to 
see that the mirror will be updated after X minutes.

Thanks!


___
kallithea-general mailing list
kallithea-general@sfconservancy.org
http://lists.sfconservancy.org/mailman/listinfo/kallithea-general


Issue #166: Support "hgweb" (and maybe gitweb) (conservancy/kallithea)

2015-10-09 Thread André Klitzing
New issue 166: Support "hgweb" (and maybe gitweb)
https://bitbucket.org/conservancy/kallithea/issues/166/support-hgweb-and-maybe-gitweb

André Klitzing:

Hi!

I like to request that kallithea could support "hgweb" interface for a separate 
path like "https://kallithea-scm.org/hgweb/repos/kallithea/; as "hg serve" or 
"SCM-Manager" does.

We use reviewboard [1] for our repository. RB needs access to a "hgweb" of the 
repository to get all information. Even our own scripts needs access to the 
REST-API of Mercurial like "http://hgweb/repon/branches?style=json;.

So it would be helpful if kallithea could provide the hgweb/gitweb interface, 
too. SCM-Manager [2] also provides it as it forks a separate python process for 
Mercurial.

[1] https://www.reviewboard.org
[2] https://bitbucket.org/sdorra/scm-manager/



___
kallithea-general mailing list
kallithea-general@sfconservancy.org
http://lists.sfconservancy.org/mailman/listinfo/kallithea-general


Issue #164: Support for http/https proxy (with proxy exception) (conservancy/kallithea)

2015-10-09 Thread André Klitzing
New issue 164: Support for http/https proxy (with proxy exception)
https://bitbucket.org/conservancy/kallithea/issues/164/support-for-http-https-proxy-with-proxy

André Klitzing:

Hi there!

We want to use kallithea behind a company proxy. As we use "remote repository 
clone" we need to add a http/https proxy. Most time the repository is available 
in internal network and don't need any proxy. Sometimes we need the proxy to 
get external repositories.

So it would be very helpful if the admin settings proxy "http/https proxies and 
proxy exceptions".
Hopefully this is easy to implement since python already implemented proxy 
support.

Thanks!


___
kallithea-general mailing list
kallithea-general@sfconservancy.org
http://lists.sfconservancy.org/mailman/listinfo/kallithea-general


[PATCH 1 of 3] files: support annotation on files larger than cut_off_limit

2015-10-09 Thread Thomas De Schampheleire
# HG changeset patch
# User Thomas De Schampheleire 
# Date 1444319150 -7200
#  Thu Oct 08 17:45:50 2015 +0200
# Node ID edc4bb70910a7ae489c600dc151553c44259ba0d
# Parent  23a86f1c33a1e64b4ae150b16749f6c629bee149
files: support annotation on files larger than cut_off_limit

When requesting the annotation for a file larger than the cut_off_limit
configured in the ini file, the only current option is to click the useless
'show as raw' (which is not an annotation).

Replace it with a link 'Show full annotation anyway' instead.

diff --git a/kallithea/controllers/files.py b/kallithea/controllers/files.py
--- a/kallithea/controllers/files.py
+++ b/kallithea/controllers/files.py
@@ -137,6 +137,7 @@ class FilesController(BaseRepoController
 c.f_path = f_path
 c.annotate = annotate
 cur_rev = c.changeset.revision
+c.fulldiff = request.GET.get('fulldiff')
 
 # prev link
 try:
diff --git a/kallithea/templates/files/files_source.html 
b/kallithea/templates/files/files_source.html
--- a/kallithea/templates/files/files_source.html
+++ b/kallithea/templates/files/files_source.html
@@ -63,15 +63,19 @@
   ${_('Binary file (%s)') % c.file.mimetype}
 
   %else:
-%if c.file.size < c.cut_off_limit:
+%if c.file.size < c.cut_off_limit or c.fulldiff:
 %if c.annotate:
   
${h.pygmentize_annotation(c.repo_name,c.file,linenos=True,anchorlinenos=True,lineanchors='L',cssclass="code-highlight")}
 %else:
   
${h.pygmentize(c.file,linenos=True,anchorlinenos=True,lineanchors='L',cssclass="code-highlight")}
 %endif
 %else:
-${_('File is too big to display')} ${h.link_to(_('Show as raw'),
-
h.url('files_raw_home',repo_name=c.repo_name,revision=c.file_changeset.raw_id,f_path=c.f_path))}
+${_('File is too big to display')}
+%if c.annotate:
+  ${h.link_to(_('Show full annotation anyway'), 
h.url.current(fulldiff=1, **request.GET.mixed()))}
+%else:
+  ${h.link_to(_('Show as raw'), 
h.url('files_raw_home',repo_name=c.repo_name,revision=c.file_changeset.raw_id,f_path=c.f_path))}
+%endif
 %endif
   %endif
 
___
kallithea-general mailing list
kallithea-general@sfconservancy.org
http://lists.sfconservancy.org/mailman/listinfo/kallithea-general


Re: Issue #161: No such table error with celery (conservancy/kallithea)

2015-10-09 Thread Michael V. DePalatis
Hi Dominik,

On 10/09/2015 11:20 AM, Dominik Ruf wrote:
> It seems to me that celery is not using the same db as kallithea.

That seems quite likely based on the traceback. I am temporarily putting
this on hold though as I work on trying to get things converted to use
Celery >= 3.1 (which is proving rather difficult since some things were
changed significantly and I can't seem to find a good guide on how to
update the specific changes that affect Kallithea; but I'll probably
start a new thread on that later if I continue to have difficulties).
For anyone interested, the current status lives in the celery3 branch
here: https://bitbucket.org/mivade/kallithea

> How do you start celery?

I started it using the method shown in the documentation
(http://docs.kallithea-scm.org/en/latest/setup.html#celery-configuration):

  $ paster celeryd my.ini

> Are you using the same .ini file for celery and kallithea?

Yes, as instructed to in the documentation.

Thanks,
Mike



signature.asc
Description: OpenPGP digital signature
___
kallithea-general mailing list
kallithea-general@sfconservancy.org
http://lists.sfconservancy.org/mailman/listinfo/kallithea-general


[PATCH 2 of 3] files: line up styling of 'File too big' message

2015-10-09 Thread Thomas De Schampheleire
# HG changeset patch
# User Thomas De Schampheleire 
# Date 1444326710 -7200
#  Thu Oct 08 19:51:50 2015 +0200
# Node ID 0252389702c09e1b8bddcc742199da1de212f5ec
# Parent  edc4bb70910a7ae489c600dc151553c44259ba0d
files: line up styling of 'File too big' message

Similar messages about 'Changeset too big to display' in the changeset and
pullrequest code are wrapped in an  tag.
Follow the same style when showing files or annotations.

diff --git a/kallithea/templates/files/files_source.html 
b/kallithea/templates/files/files_source.html
--- a/kallithea/templates/files/files_source.html
+++ b/kallithea/templates/files/files_source.html
@@ -70,12 +70,14 @@
   
${h.pygmentize(c.file,linenos=True,anchorlinenos=True,lineanchors='L',cssclass="code-highlight")}
 %endif
 %else:
+
 ${_('File is too big to display')}
 %if c.annotate:
   ${h.link_to(_('Show full annotation anyway'), 
h.url.current(fulldiff=1, **request.GET.mixed()))}
 %else:
   ${h.link_to(_('Show as raw'), 
h.url('files_raw_home',repo_name=c.repo_name,revision=c.file_changeset.raw_id,f_path=c.f_path))}
 %endif
+
 %endif
   %endif
 
___
kallithea-general mailing list
kallithea-general@sfconservancy.org
http://lists.sfconservancy.org/mailman/listinfo/kallithea-general