I wasn't sure if my attachment made it through the mailing list. Is there an
issue/report/task created for this which I can continue following instead of
through the mailing list? I couldn't figure out how to create an issue on the
fossil-scm site.
On Mar 18, 2015, at 10:30 AM, die.drachen
On 3/18/15, die.drachen die.drac...@gmail.com wrote:
Unfortunately I'm unable to distribute the repo, which is also quite large
(~730mb .fossil file, 93k commits). Are there additional measures I can
take to get diagnostic information?
Compile your own Fossil from trunk sources, using options
I attached the output (using lldb instead of gdb).
$ lldb fossil
(lldb) target create fossil
Current executable set to 'fossil' (x86_64).
(lldb) run test-http mimjava.fossil
Process 87976 launched: '/.../fossil' (x86_64)
GET /timeline?n=421y=all
Process 87976 stopped
* thread #1: tid = 0x38540d,
Unfortunately I'm unable to distribute the repo, which is also quite large
(~730mb .fossil file, 93k commits). Are there additional measures I can take
to get diagnostic information?
Christopher
On Mar 17, 2015, at 7:09 PM, Richard Hipp d...@sqlite.org wrote:
On 3/17/15, die.drachen
Thus said die.drachen die.drac...@gmail.com on Wed, 18 Mar 2015 00:58:41
-0400:
Unfortunately I'm unable to distribute the repo, which is also quite
large (~730mb .fossil file, 93k commits). Are there additional
measures I can take to get diagnostic information?
You could ensure
With fossil 1.31 [2e7c40dbdd] on OSX I ran locally:
$ fossil server
Then on the timeline page for the Max field, when I enter values between
421-449, the server doesn't respond. Using curl:
$ curl http://localhost:8080/timeline?n=421y=allv=0
http://localhost:8080/timeline?n=421y=allv=0
curl:
On 3/17/15, die.drachen die.drac...@gmail.com wrote:
With fossil 1.31 [2e7c40dbdd] on OSX I ran locally:
$ fossil server
Then on the timeline page for the Max field, when I enter values between
421-449, the server doesn't respond. Using curl:
$ curl
7 matches
Mail list logo
