urosm
/
ikiwiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

response

master
joey 2007-03-16 19:20:36 +00:00
parent f6a15f38c2
commit 4be6ccbc02
2 changed files with 16 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/bugs/svn-commit-hanging.mdwn
View File

@ -1 +1,3 @@
When I'm committing a page via the Web, Ikiwiki hangs at the `svn commit` stage. I'm sure that this is a result of all my local modifications, so there's no need to consider this a bug per se, but I'd be interested in hearing whether anybody else has seen this. -- [[Ben]]
When I'm committing a page via the Web, Ikiwiki hangs at the `svn commit` stage. I'm sure that this is a result of all my local modifications, so there's no need to consider this a bug per se, but I'd be interested in hearing whether anybody else has seen this. -- [[Ben]]
What kinds of local modifications are those? --[[Joey]]

14
doc/subversion/discussion.mdwn
View File

@ -1 +1,13 @@
If the user interrupts the page loading during the running of `svn commit`, the repository will be left in an inconsistent state. The probability of this happening increases with the size of the repository and the number of plugins installed, because these both affect how long the post-commit hook takes to run. (The core issue, I guess, is that we're abusing the concept of a "working copy" by giving everybody the same one). Here are the main solutions that I can see: (1) CGI queues commits so that a single process can act upon them sequentially, or (2) optionally divorce the `ikiwiki --refresh` from the `svn commit` so that commits happen faster. -- [[Ben]]
If the user interrupts the page loading during the running of `svn commit`,
the repository will be left in an inconsistent state. The probability of
this happening increases with the size of the repository and the number of
plugins installed, because these both affect how long the post-commit hook
takes to run. (The core issue, I guess, is that we're abusing the concept
of a "working copy" by giving everybody the same one). Here are the main
solutions that I can see: (1) CGI queues commits so that a single process
can act upon them sequentially, or (2) optionally divorce the `ikiwiki
--refresh` from the `svn commit` so that commits happen faster. -- [[Ben]]
I'm not aware of web servers, at least apache, killing cgi processes when
the user stops a page load. If this is happening ikiwiki should be able to
avoid it by blocking whatever signal is causing it to terminate. --[[Joey]]