Mark Schlieker
Activity
Reported issues: 4
09/02/2009
- 03:11 PM SupoSE Bug #230: Indexer drops information probably when creating summary
- Hi. When running the indexer without scheduler the index is created properly. There is no summary then but I think the summery is only created for the scheduler, isnt it? Regards, Mark
08/27/2009
- 11:01 AM SupoSE Bug #230: Indexer drops information probably when creating summary
- Mark Schlieker wrote: > The ini-file is not really exciting. It looks like this: > The format got lost, here it is preformatted: ...
- 10:59 AM SupoSE Bug #230: Indexer drops information probably when creating summary
- The ini-file is not really exciting. It looks like this: [PROJECTXY] url = https://svn.domain.org/repos indexusername = myusername indexpassword = mypassword fromrev = 0 torev = HEAD resultindex = summary cron = 0 30 13,22 * * ?
08/26/2009
- 04:02 PM SupoSE Bug #230: Indexer drops information probably when creating summary
- I now rerun the indexing but without the scheduler option. I have the feelin it has to do with the task which creates the summary. I had over 10 GB of index after the index run approx. for 4 days and in the end it decreased to only 200 MB.
- 03:44 PM SupoSE Bug #230: Indexer drops information probably when creating summary
- I recently indexed a very large svn repository. It has over 50 GB of contents and several 100,000 files. It took about a week for the indexing process to finish and I noticed that the total size of the files in the index folder decreased dramatica...
- Hello, as I seem not to have the right to write in Wiki I like to recomment to update the page "Fields" and add dfilename and dpath as new fields see http://supose.soebes.de/wiki/supose/Fields Kind regards, Mark
06/26/2009
- 10:05 AM SupoSE Bug #217: Sudden allocation of memory makes tool unusable for large repositories
- It managed to scan 7.75% of what it was supposed to scan which is 5365 revisions due to the information it outputs to the command line window while running.
- 09:59 AM SupoSE Bug #217: Sudden allocation of memory makes tool unusable for large repositories
- I have a very large SVN repository to scan which has about 55 GB of data and over 11,000 commits/log entries. I used SupoSE version 0.5.1 before and it managed to scan the whole repository but version 0.6.1-385 suddenly (after scanning for about 1...
05/04/2009
- Hello, SupoSE can not only search for a file name inside a SVN repository but also for many other items. This is possible because it makes use of "fields". There is also a field "contents" which shall probably enable the user to search the cont...
02/23/2009
- I have a question regarding version numbering. When you take a look at section "Files":/projects/list_files/supose you will see releases of SupoSE named Ceres, Europa, etc. Moreover each release has a version number which is made of a numbering ...
Also available in: Atom