On Thu, Jul 16, 2015 at 7:06 AM, Andy Bradford
wrote:
> Hello,
>
> Has anyone (other than me) tested the changes for enabling amending
> checkins from the command line in the check-in-edit branch?
>
> I think it's ready, but it certainly could use additional testing given
> that it also
i will be happy to try it out this evening - it's a long overdue feature.
- stephan
Sent from a mobile device, possibly from bed. Please excuse brevity and
typos.
On Jul 16, 2015 7:06 AM, "Andy Bradford" wrote:
> Hello,
>
> Has anyone (other than me) tested the changes for enabling amen
Hello,
Has anyone (other than me) tested the changes for enabling amending
checkins from the command line in the check-in-edit branch?
I think it's ready, but it certainly could use additional testing given
that it also includes changes that affect the web ci_edit page
(primarily
Thus said Philip Bennefall on Wed, 15 Jul 2015 20:22:07 +0200:
> About a month ago I reported having some issues with the standalone
> Fossil server, where it would slow down significantly after running
> for an extended period.
What specifically is slow? Clone? Sync? Accessing pages serv
Tcpwrappers or some reverse name lookup issues? Running ktrace, ptrace, or
whatever your system provides might be telling.
On Jul 15, 2015 3:06 PM, "Philip Bennefall" wrote:
> Hi there,
>
> Thanks to all who responded! I decided to try running Fossil through
> xinetd instead, and am now seeing al
> Please try again now.
Fixed in 31c3c599ffb1b449, thank you.
However I still believe that someday the following would be fixed too:
http://localhost:8080/doc (and doc/) should search for tip/index.html
and tip/index.md in addition to index.wiki. Same with 404.md.
http://localhost:8080/doc/cko
Hi there,
Thanks to all who responded! I decided to try running Fossil through
xinetd instead, and am now seeing almost instantaneous load times again.
The problem was never Fossil's actual processing time displayed at the
bottom of each page (that was always just a few milliseconds), but
rat
On 7/15/15, Sergey Sfeli wrote:
> http://www.fossil-scm.org/fossil/info/c99b4e34dd1db2cc does not fix an
> issue 1 completely: http://localhost:8080/doc//index.md still crashes.
>
Please try again now.
--
D. Richard Hipp
d...@sqlite.org
___
fossil-user
http://www.fossil-scm.org/fossil/info/c99b4e34dd1db2cc does not fix an
issue 1 completely: http://localhost:8080/doc//index.md still crashes.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman
Hello Philip,
On 15 July 2015 at 11:22, Philip Bennefall wrote:
> Now, Fossil has been running on the server since that time and has become
> very slow again.
What _is_ slow? Loading the pages for me took about 0.004s. Your
initial email reported "taking 15 seconds or so to pull up the front
page
Some more thoughts:
On Jul 15, 2015, at 12:22 PM, Philip Bennefall wrote:
>
> An example of a repo on my server is:
> http://server.blastbay.com/blastmidi/
What’s the largest repo on that server? That one is less than a meg and only
has 3 checkins:
http://server.blastbay.com/blastmidi/st
On Jul 15, 2015, at 12:22 PM, Philip Bennefall wrote:
>
> Would any of you Linux gurus be willing to give me some commands I could run
> on the fossil process to extract useful statistics?
Run top(1). Is fossil one of the top processes in its default mode, which
sorts by CPU usage?
If not, s
On 7/15/15, Philip Bennefall wrote:
> Hi all,
>
> About a month ago I reported having some issues with the standalone
> Fossil server, where it would slow down significantly after running for
> an extended period. At that time I had just restarted the process, so
> was not able to gather any meani
Hi all,
About a month ago I reported having some issues with the standalone
Fossil server, where it would slow down significantly after running for
an extended period. At that time I had just restarted the process, so
was not able to gather any meaningful statistics in order to help
diagnose
Hi,
Apparently the problem only occurs on my MacBook. On other OS’es the fix seems
to work and I was able to create a docker container that works as expected.
The Not found message probably comes from that there are no fossils in the
directory. Maybe it would be nice to handle that case.
I ins
On Wed, 15 Jul 2015, Sergei Gavrikov wrote:
> Hi,
>
> Fossil falls at dry run of merge for one my repository:
>
> % f merge -n trunk
> [snip]
> Fossil internal error: failed to save undo information for path:
Below prevents 'fossil panic' for my case
Sergei
Index: src/undo.c
Hi,
Fossil falls at dry run of merge for one my repository:
% f merge -n trunk
[snip]
Fossil internal error: failed to save undo information for path:
What may a reason be? Just in a case, fossil version
% fossil version -v
This is fossil version 1.33 [b9b9d7e739] 2015-07-15 10:38:24
17 matches
Mail list logo
