[fossil-users] Markdown rules for Fossil Wiki
I understand from the wiki formatting rules page that links can be created via [mylink], but this doesn't work if I use markdown. I can use the [thename](target_link) markdown style, but that is a generic link and I seem to have to specify the full link and not just the wiki page name. Is there a proper way to specify a wiki-internal link using markdown or must I use the HTML-style wiki formatting rules? Gerald. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil process hanging on sync to remote server?
On Sat, May 10, 2014 at 1:03 AM, Stephan Beal sgb...@googlemail.com wrote:
For me fossil builds with -g (debug) flags by default, so you shouldn't
have to rebuild.
I ended up recompiling fossil just to be sure. On Mac OSX Mavericks, gdb
has been replaced by lldb.
I managed to get the process to hang again (it hadn't completed in over 10
minutes during a sync). I attached to it and went looking up the frames one
by one.
Here are the frames:
frame #0: 0x7fff8aef59f0 libsystem_kernel.dylib`read + 8
frame #1: 0x7fff8fbfd84c libcrypto.0.9.8.dylib`conn_read + 76
frame #2: 0x7fff8fbf7264 libcrypto.0.9.8.dylib`BIO_read + 100
frame #3: 0x7fff86b6513d libssl.0.9.8.dylib`ssl3_read_n + 365
frame #4: 0x7fff86b65b9f libssl.0.9.8.dylib`ssl3_read_bytes + 735
frame #5: 0x7fff86b63dec libssl.0.9.8.dylib`ssl3_read + 156
frame #6: 0x7fff86b4e4c9 libssl.0.9.8.dylib`ssl_read + 73
frame #7: 0x7fff8fbf7264 libcrypto.0.9.8.dylib`BIO_read + 100
frame #8: 0x000105719ba2 fossil`ssl_receive(NotUsed=unavailable,
pContent=unavailable, N=unavailable) + 50 at http_ssl.c:399
396 size_t got;
397 size_t total = 0;
398 while( N0 ){
- 399 got = BIO_read(iBio, pContent, N);
400 if( got=0 ) break;
401 total += got;
402 N -= got;
So, it's hanging in the BIO_read function.
Global/static variables (command: ta v) are:
(SSL_CTX *) sslCtx = 0x7fa1c2e039b0
(char *) sslErrMsg = 0x
(SSL *) ssl = 0x7fa1c2e04430
(BIO *) iBio = 0x7fa1c2e043c0
Frame variables (fr v) are unfortunately:
(void *) NotUsed = variable not available
(void *) pContent = variable not available
(size_t) N = variable not available
(size_t) total = 0
(size_t) got = variable not available
Going up a couple more frames gives context to where in the code it is
stalling but I'm not sure whether it gives any insight to why. Perhaps if
someone could give some guidance on how I can investigate further I can
help diagnose. Here are the remaining frames all the way up to main:
frame #9: 0x00010571a3a6 fossil`transport_fetch(pUrlData=unavailable,
zBuf=0x7fa1c2e078b0, N=1000) + 102 at http_transport.c:311
308 }
309 }else if( pUrlData-isHttps ){
310 #ifdef FOSSIL_ENABLE_SSL
- 311 got = ssl_receive(0, zBuf, N);
312 #else
313 got = 0;
314 #endif
(lldb) up
frame #10: 0x00010571a548 fossil`transport_receive_line [inlined]
transport_load_buffer(pUrlData=0x00010589f430) + 236 at
http_transport.c:393
390 transport.pBuf = pNew;
391 }
392 if( N0 ){
- 393 i = transport_fetch(pUrlData, transport.pBuf[transport.nUsed],
N);
394 if( i0 ){
395 transport.nRcvd += i;
396 transport.nUsed += i;
(lldb) up
frame #11: 0x00010571a45c
fossil`transport_receive_line(pUrlData=0x00010589f430) + 76 at
http_transport.c:416
413 i = iStart = transport.iCursor;
414 while(1){
415 if( i = transport.nUsed ){
- 416 transport_load_buffer(pUrlData, pUrlData-isSsh ? 2 : 1000);
417 i -= iStart;
418 iStart = 0;
419 if( i = transport.nUsed ){
(lldb) up
frame #12: 0x000105718815
fossil`http_exchange(pSend=0x7fff5a518640, pReply=0x7fff5a518620,
useLogin=1, maxRedirect=20) + 1301 at http.c:206
203 */
204 closeConnection = 1;
205 iLength = -1;
- 206 while( (zLine = transport_receive_line(GLOBAL_URL()))!=0
zLine[0]!=0 ){
207 /* printf([%s]\n, zLine); fflush(stdout); */
208 if( fossil_strnicmp(zLine, http/1., 7)==0 ){
209 if( sscanf(zLine, HTTP/1.%d %d, iHttpVersion, rc)!=2 )
goto write_err;
(lldb) up
frame #13: 0x00010576b1e3 fossil`client_sync(syncFlags=unavailable,
configRcvMask=unavailable, configSendMask=unavailable) + 1955 at
xfer.c:1560
1557}
1558fflush(stdout);
1559/* Exchange messages with the server */
- 1560if( http_exchange(send, recv, (syncFlags SYNC_CLONE)==0 ||
nCycle0,
1561MAX_REDIRECTS) ){
1562 nErr++;
1563 break;
(lldb) up
frame #14: 0x00010574d2a9 fossil`autosync(flags=unavailable) + 313 at
sync.c:75
72if( find_option(verbose,v,0)!=0 ) flags |= SYNC_VERBOSE;
73fossil_print(Autosync: %s\n, g.urlCanonical);
74url_enable_proxy(via proxy: );
- 75rc = client_sync(flags, configSync, 0);
76if( rc ) fossil_warning(Autosync failed);
77return rc;
78 }
(lldb) up
frame #15: 0x0001056f9f85 fossil`commit_cmd + 5365 at checkin.c:1927
1924 db_end_transaction(0);
1925
1926 if( !g.markPrivate ){
- 1927autosync(SYNC_PUSH|SYNC_PULL);
1928 }
1929 if( count_nonbranch_children(vid)1 ){
1930fossil_print( warning: a fork has occurred *\n);
(lldb) up
frame #16: 0x000105726195 fossil`main(argc=unavailable,
argv=unavailable) + 2325 at main.c:701
698 fossil_exit(1);
699 }
700 atexit( fossil_atexit );
- 701 aCommand[idx].xFunc();
702 fossil_exit(0);
[fossil-users] Fossil process hanging on sync to remote server?
On Fri, May 9, 2014 at 2:25 AM, Stephan Beal sgb...@googlemail.com wrote:
Other than that, i can't comment: i've only seen such behaviour in 'ping'
on Solaris, where it can cause a backlog of cronjobs, which causes all
other jobs to queue up until you kill the pings, at which point _all_
queued jobs, since the queue limit was reached (several days in my case),
run in rapid succession!
(Changed subject line to reflect new topic)
Well, it's happened again.
This time I have the cron logging on. I get a mail message every time a
cronjob completes, and it's distinctly missing the one for the fossil sync
session that is hung. If I look at processes, I get this (notice it
executed at 9:05am, about 5 minutes after cronjob started and the entire
cronjob, if successful, only takes about 30 seconds):
$ uname -a
Darwin mycomp.local 13.1.0 Darwin Kernel Version 13.1.0: Thu Jan 16
19:40:37 PST 2014; root:xnu-2422.90.20~2/RELEASE_X86_64 x86_64
$ ps auxww | grep fossil
USER PID %CPU %MEM VSZRSS TT STAT STARTED
TIME COMMAND
xxx 7619 0.0 0.2 2490036 29836 ?? S 9:05AM
0:13.80 /usr/local/bin/fossil commit --no-warnings -m Fri May 9 09:05:41
PDT 2014
The cronjob log for the cronjob executing AFTER the one that hung says this:
added 3 files, deleted 0 files
/usr/local/bin/fossil: database is locked: {REPLACE INTO
config(name,value,mtime)
VALUES('last-sync-url','my repo url',now())}
If you have recently updated your fossil executable, you might
need to run fossil all rebuild to bring the repository
schemas up to date.
So, there is definitely a problem here. It doesn't happen all the time, but
enough that it occurs at least once a day.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Is it advisable to put a .fossil repository on Dropbox?
On Wed, May 7, 2014 at 8:15 AM, Stephan Beal sgb...@googlemail.com wrote: The lock you're seeing is almost certainly your dropbox and should be harmless. sqlite locks the db as needed, and Dropbox should recognize that and not touch the file as long as it's locked (but posix locks are advisory locks, not required to be honored!). Actually, I may have tracked it down now. It turns out to be a hung fossil process. I no longer think it's due to Dropbox. I stopped using Dropbox and started syncing to a private remote server. I use cron to do a commit sync every hour, and fossil is run from a bash script via cron. It seems that after a couple of successful runs, the fossil process starts to hang. I get a bunch of them when I do ps aux, and when I kill them, the commits start working again. I've seen references to fossil hanging before (but can't find it now). Is this a known issue? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Is it advisable to put a .fossil repository on Dropbox?
I have a fossil repository that I use on two machines, one at work and one at home. For this one, I'd rather not host it at an online location. So I tried to to put the fossil file on Dropbox instead so that Dropbox will automatically sync the file between the two machines. Since I've tried to do this, I occasionally get database is locked errors when trying to commit on one of the two machines. Could I be corrupting the fossil file somehow this way? Is this advisable? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Merging two leaves not on the same graph?
Too big. Chiselapp has an 8MB upload size limit. On Wed, Apr 30, 2014 at 11:44 PM, Andy Goth andrew.m.g...@gmail.com wrote: On 5/1/2014 12:24 AM, Gerald Gutierrez wrote: I've got a fossil repository that has had two years' worth of history. Recently, I decided to host it on chiselapp, so I created a repository on chiselapp with the same project-id as my repository. Did you use the Upload Repository feature? -- Andy Goth | andrew.m.goth/at/gmail/dot/com ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Merging two leaves not on the same graph?
I've got a fossil repository that has had two years' worth of history. Recently, I decided to host it on chiselapp, so I created a repository on chiselapp with the same project-id as my repository. I then pushed my local repository to the chiselapp repository and then looked at the timeline and realized that I have two leaves now but they are not on the same directed graph (http://imgur.com/eMlgTgk). Then I read at the fossil web site ( http://www.fossil-scm.org/index.html/doc/tip/www/branching.wiki) that fossil keeps all check-ins in a single DAG, but the two leaves I have are clearly on different DAGs. When I try to merge them, fossil complains: Merging fork [040afa12232413ae] at 2014-05-01 02:08:30 by xxx: initial empty check-in cannot find a common ancestor between the current checkout and Note that after the and it doesn't say anything. So now I'm confused. Should/can I merge these two leaves, or just leave it alone, or is the repository now in an inconsistent state? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
