Re: [fossil-users] Fossil error when pushing
On 20-2-2013 22:59, Stephan Beal wrote: On Wed, Feb 20, 2013 at 10:44 PM, Arnel Legaspi wrote: Error: not authorized to writet: 0 received: 0 The not authorized to writet does not come from fossil: stephan@tiny:~/cvs/fossil/fossil/src$ grep writet *.c It looks like the 't' at the end of 'writet' stems from the word 'sent' that went with the 'received' that follows. It would appear that the 'sent: 0 received: 0' was written, followed by a carriage return WITHOUT linefeed, and then the error message was printed, overwriting the prior message (partially, in this case). Which is why grepping for 'writet' will not find anything. :-) (This is something I've seen happen several times already: error messages overwriting existing 'regular' output; perhaps it’s a Windows console issue). -- Martijn Coppoolse ___ 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 svn conversion gets confused if last svn checkin is on a branch
On 20-2-2013 22:34, Warren Young wrote: But before looking at it, I want to stress that I don't believe Fossil has lost any data, it's just that the default Files view shows the last branch I worked on, rather than the trunk as I expected. This sounds as if the 'Files' tab of your repository links to http://server/repo/dir?ci=tip whereas you expected it to link to http://server/repo/dir?ci=trunk 'tip' is an alias for the most recent check-in. If your most recent check-in was not in trunk, you won’t see trunk on that page. You can easily adjust that in the Admin/Header section of the web interface. -- Martijn Coppoolse ___ 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 json stat output
On Thu, Feb 21, 2013 at 3:04 AM, Ross Berteig r...@cheshireeng.com wrote: So I second the notion of a separate json extra command to signal that the additional work really is wanted. I have no strong opinions about the structure of the payload, other than the segregation of extras from other changes. Perhaps I'd even go so far as to imagine json status, json changes, and json extras where status doesn't include anything more than an indication of whether changes are known to exist, and the two commands changes and extras are analogous to their CLI namesakes. Interestingly, the changes and status commands are internally the same code except for the header info output by status. So whether or not to split status/changes into two commands or have as option to the status command, e.g. (json status --changes), is up for discussion. i won't be able to work on it until the weekend, so bikeshedding season is open until then. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] Making the go tool support fossil
On Thu, Feb 21, 2013 at 8:33 AM, Konstantin Khomoutov flatw...@users.sourceforge.net wrote: IOW, that shell pipeline was just an example demonstrated to you, so don't be too attached to the fact it requires a shell. That's correct, but Lluis is right in suggesting that we should have a command like: fossil ping repo-address which can piggyback on the protocols supported by cloning (ssh/http[s]), but: a) does no authentication checks (because we cannot know which permissions would be required by later commands). b) does no useful work - simply checks for connectivity. c) returns a trivial response, e.g. OK or FAIL, and uses the exit code to report success/failure. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] Making the go tool support fossil
On Thu, Feb 21, 2013 at 10:24:27AM +0100, Stephan Beal wrote: On Thu, Feb 21, 2013 at 8:33 AM, Konstantin Khomoutov flatw...@users.sourceforge.net wrote: IOW, that shell pipeline was just an example demonstrated to you, so don't be too attached to the fact it requires a shell. That's correct, but Lluis is right in suggesting that we should have a command like: fossil ping repo-address which can piggyback on the protocols supported by cloning (ssh/http[s]), but: a) does no authentication checks (because we cannot know which permissions would be required by later commands). b) does no useful work - simply checks for connectivity. c) returns a trivial response, e.g. OK or FAIL, and uses the exit code to report success/failure. Well it would be better if it reported something like 'fossil info' for tip. :) Just to make the command a bit more useful. The go tool will use it for 'ping' basically, though. Regards, Lluís. ___ 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] Making the go tool support fossil
On Thu, 21 Feb 2013 10:28:52 +0100 Lluís Batlle i Rossell vi...@viric.name wrote: [...] That's correct, but Lluis is right in suggesting that we should have a command like: fossil ping repo-address which can piggyback on the protocols supported by cloning (ssh/http [s]), but: a) does no authentication checks (because we cannot know which permissions would be required by later commands). b) does no useful work - simply checks for connectivity. c) returns a trivial response, e.g. OK or FAIL, and uses the exit code to report success/failure. Well it would be better if it reported something like 'fossil info' for tip. :) This might contradict point (a) above in certain setups, does it? I mean that my own repos require authentication only for pushing but supposedly there might be some use for locked down private repos. I just don't know is it possible to fully lock a Fossil repo so that any access to it must be authenticated. ___ 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] Making the go tool support fossil
On Thu, Feb 21, 2013 at 02:13:14PM +0400, Konstantin Khomoutov wrote: On Thu, 21 Feb 2013 10:28:52 +0100 Lluís Batlle i Rossell vi...@viric.name wrote: [...] That's correct, but Lluis is right in suggesting that we should have a command like: fossil ping repo-address which can piggyback on the protocols supported by cloning (ssh/http [s]), but: a) does no authentication checks (because we cannot know which permissions would be required by later commands). b) does no useful work - simply checks for connectivity. c) returns a trivial response, e.g. OK or FAIL, and uses the exit code to report success/failure. Well it would be better if it reported something like 'fossil info' for tip. :) This might contradict point (a) above in certain setups, does it? I mean that my own repos require authentication only for pushing but supposedly there might be some use for locked down private repos. I just don't know is it possible to fully lock a Fossil repo so that any access to it must be authenticated. I find this behaviour reasonable: If the url had a username, it could ask for a password. And in any case, if the rights aren't ok to fetch the info, it should fail. I'd make it work with the 'timeline' or 'clone' permission flags. ___ 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] Making the go tool support fossil
On Thu, Feb 21, 2013 at 11:16 AM, Lluís Batlle i Rossell vi...@viric.namewrote: I'd make it work with the 'timeline' or 'clone' permission flags. Using the clone rights for this purpose sounds reasonable to me. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] build error: 'Global' has no member named 'dontKeepUrl'
Hi Could you, please, add it to main.c:Global: Thanks Sergei --- checkout: 75e483899e28a533c7f17bb179acd9c10e9f3b60 2013-02-21 08:15:41 UTC tags: trunk comment: unused variables (user: jan.nijtmans) changes: None. Already up-to-date ../src/http_transport.c: In function ‘test_ssh_far_side_cmd’: ../src/http_transport.c:271: warning: ignoring return value of ‘system’, declared with attribute warn_unused_result ../src/json.c: In function ‘json_g_to_json’: ../src/json.c:1402: error: ‘Global’ has no member named ‘dontKeepUrl’ make: *** [bld/json.o] Error 1 ___ 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] build error: 'Global' has no member named 'dontKeepUrl'
2013/2/21 Sergei Gavrikov sergei.gavri...@gmail.com: Hi Could you, please, add it to main.c:Global: Thanks Sergei The actual commit which removed it was one earlier: 03:51:10 [6d6740dcca] Improved handling for remote repository passwords: When prompting for the password, also ask the user whether or not to remember the password, as browsers typically do for their password cache. (user: drh tags: trunk) See: https://www.fossil-scm.org/index.html/fdiff?v1=bc91379546130792v2=be285f713732c242 Fixed now. Regards, jan Nijtmans ___ 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] build error: 'Global' has no member named 'dontKeepUrl'
On Thu, 21 Feb 2013, Jan Nijtmans wrote: 2013/2/21 Sergei Gavrikov sergei.gavri...@gmail.com: Hi Could you, please, add it to main.c:Global: Thanks Sergei The actual commit which removed it was one earlier: 03:51:10 [6d6740dcca] Improved handling for remote repository passwords: When prompting for the password, also ask the user whether or not to remember the password, as browsers typically do for their password cache. (user: drh tags: trunk) See: https://www.fossil-scm.org/index.html/fdiff?v1=bc91379546130792v2=be285f713732c242 Ah, Jan, I did not mean your commit broke build (though it looks like I did), I just cut that from a build output and sent.. Sorry, next time I will dig deeper. Fixed now. Thank you! Sergei Regards, jan Nijtmans ___ 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] Is it possible to increase the sqlite timeout for fossil?
We are getting a *lot* of collisions in heavy use repos. Rather than confusing sync errors I'd like it if fossil just waited longer for the repo to come available. I think setting a 10 second timeout on sqlite would make a huge difference here. Can this be done? Thanks. ___ 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 possible to increase the sqlite timeout for fossil?
On Thu, Feb 21, 2013 at 10:24 AM, Matt Welland estifo...@gmail.com wrote: We are getting a *lot* of collisions in heavy use repos. Rather than confusing sync errors I'd like it if fossil just waited longer for the repo to come available. I think setting a 10 second timeout on sqlite would make a huge difference here. Can this be done? Timeout is currently 5 seconds: http://www.fossil-scm.org/fossil/artifact/35a237cbfde?ln=723 You could change that and recompile. But before you do, first make sure you are in WAL mode. Can you post the /stat page for your repository - the equivalent of (http://www.fossil-scm.org/fossil/stat)? Thanks. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ 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 possible to increase the sqlite timeout for fossil?
Interesting that the timeout is already 5 seconds. What happens is
sync fails and then users are confused. Perhaps this is not a timeout?
Note that this is direct file system access. I think suppressing the
sqlite3 error would help and a try again? Y/n prompt.
This is what we see:
New_Version: 5df265af2129cc9d526860abc5897d084aa5ae25
Autosync: file://.blah.fossil
Bytes Cards Artifacts Deltas
Sent:5152 71 0 4
Error: Database error: unable to open database file
INSERT INTO rcvfrom(uid, mtime, nonce, ipaddr)VALUES(1,
julianday('now'), NULL, '127.0.0.1')
Received: 159 1 0 0
Total network traffic: 2854 bytes sent, 348 bytes received
fossil: Autosync failed
Stat output:
Repository Size: 214505472 bytes
Number Of Artifacts: 18929 (stored as 7411 full text and 11518 delta blobs)
Uncompressed Artifact Size: 108372 bytes average, 528150528 bytes max,
2051280245 bytes total
Compression Ratio: 9:1
Number Of Check-ins: 3411
Number Of Files: 14198
Number Of Wiki Pages: 11
Number Of Tickets: 30
Duration Of Project: 743 days or approximately 2.03 years
Project ID: b711128a80477cdb2f9a91b663dd6b2e8083c0b0
Server ID: b7aa6d92b218bd8086de653d1b7b58d7fac84c02
Fossil Version: 1.22 2012-03-19 12:45:47 [5dd5d39e7c] (gcc-4.4.1)
SQLite Version: 2012-03-16 00:28:11 [74eadeec34] (3.7.11)
Database Stats: 209478 pages, 1024 bytes/page, 113 free pages, UTF-8,
delete mode
On Thu, Feb 21, 2013 at 8:36 AM, Richard Hipp d...@sqlite.org wrote:
On Thu, Feb 21, 2013 at 10:24 AM, Matt Welland estifo...@gmail.com wrote:
We are getting a *lot* of collisions in heavy use repos. Rather than
confusing sync errors I'd like it if fossil just waited longer for the
repo to come available. I think setting a 10 second timeout on sqlite
would make a huge difference here. Can this be done?
Timeout is currently 5 seconds:
http://www.fossil-scm.org/fossil/artifact/35a237cbfde?ln=723
You could change that and recompile. But before you do, first make sure you
are in WAL mode. Can you post the /stat page for your repository - the
equivalent of (http://www.fossil-scm.org/fossil/stat)?
Thanks.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
D. Richard Hipp
d...@sqlite.org
___
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
Re: [fossil-users] Is it possible to increase the sqlite timeout for fossil?
On Thu, Feb 21, 2013 at 11:21 AM, Matt Welland estifo...@gmail.com wrote: Database Stats: 209478 pages, 1024 bytes/page, 113 free pages, UTF-8, delete mode That delete mode notation on the end denotes the problem. You need to change your repository on the server to WAL mode. Do this as follows: sqlite3 $repository 'pragma journal_mode=wal' Or fossil rebuild $repository --pagesize 8192 --wal The second method will take (much) longer, but it also changes the page size from 1024 bytes to 8192 bytes, which won't make a huge difference but will help some. -- D. Richard Hipp d...@sqlite.org ___ 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 possible to increase the sqlite timeout for fossil?
On Thu, Feb 21, 2013 at 9:25 AM, Richard Hipp d...@sqlite.org wrote: On Thu, Feb 21, 2013 at 11:21 AM, Matt Welland estifo...@gmail.com wrote: Database Stats: 209478 pages, 1024 bytes/page, 113 free pages, UTF-8, delete mode That delete mode notation on the end denotes the problem. You need to change your repository on the server to WAL mode. Do this as follows: sqlite3 $repository 'pragma journal_mode=wal' Or fossil rebuild $repository --pagesize 8192 --wal The second method will take (much) longer, but it also changes the page size from 1024 bytes to 8192 bytes, which won't make a huge difference but will help some. We can't switch to WAL mode currently as these repos are accessed from multiple machines via NFS. Now that ssh is working for us we can convert over to using ssh to a central server and switch to WAL mode at the same time. Is there any downside to using ssh? How dramatic is the performance improvement with WAL mode? Thanks. -- D. Richard Hipp d...@sqlite.org ___ 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
Re: [fossil-users] Is it possible to increase the sqlite timeout for fossil?
On Thu, Feb 21, 2013 at 11:45 AM, Matt Welland estifo...@gmail.com wrote: We can't switch to WAL mode currently as these repos are accessed from multiple machines via NFS. Now that ssh is working for us we can convert over to using ssh to a central server and switch to WAL mode at the same time. Is there any downside to using ssh? How dramatic is the performance improvement with WAL mode? The big advantage of WAL mode is that readers won't block writers. That can be a huge deal on a busy site. But the biggest gains you'll see will come from using ext4 instead of nfs as our filesystem. My gut instinct is that ssh will probably work better for this. Let me know if you encounter problems with it. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] looking for guinea pigs for new help functionality
Hiho, i'm looking for guinea pigs again :), this time with minor enhancements to the online help system: support for web page-specific help. (Most pages don't have any useful help at the moment, though.) To try it out, check out the 'help-www' branch: http://fossil-scm.org/index.html/timeline?r=help-www then: fossil help help reveals a new option: fossil help --www lists the available web pages. fossil help /pagename shows the help. Note that the / prefix is necessary to avoid ambiguities (e.g. /timeline vs timeline). e.g. stephan@tiny:~/cvs/fossil/fossil$ f help /timeline.rss | head URL: /timeline.rss?y=TYPEn=LIMITtkt=UUIDtag=TAGwiki=NAMEname=FILENAME Produce an RSS feed of the timeline. TYPE may be: all, ci (show checkins only), t (show tickets only), w (show wiki only). LIMIT is the number of items to show. ... It also handles ambiguous names: stephan@tiny:~/cvs/fossil/fossil$ f help /tkt ambiguous page prefix: /tkt Matching pages: /tktedit /tktsetup_editpage/tktsetup_timeline /tkthistory /tktsetup_keytplt /tktsetup_viewpage ... From the UI, visit the /help page for a list of CLI commands (as before) and www pages (new). Alternately, visit /help?cmd=/pagename to jump right to the help, e.g. /help?cmd=/timeline.rss. If you have suggestions for improving this feature (and they don't require a complete overhaul of the built-in help mechanism), please feel free to voice them. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] looking for guinea pigs for new help functionality
On Thu, 21 Feb 2013, Stephan Beal wrote: Hiho, i'm looking for guinea pigs again :), this time with minor enhancements to the online help system: support for web page-specific help. (Most pages don't have any useful help at the moment, though.) To try it out, check out the 'help-www' branch: http://fossil-scm.org/index.html/timeline?r=help-www [snip, see details http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg11361.html] If you have suggestions for improving this feature (and they don't require a complete overhaul of the built-in help mechanism), please feel free to voice them. Hi All looks great for me. Thanks for that new built-in help topics (very useful, otherwise users have to grep this list or Fossil sources). $0.02 - I would avoid that output of the base /help URL begins itself too long (more than 1/2 of screen in $BROWSER), I would just add SEE ALSO link on a bottom the Fossil's help page (as man does). - Perhaps, it is logical to list new topics in the list Available pages with / prefix as /access_log, /admin_sql and so on. Regards, Sergei -- - stephan beal http://wanderinghorse.net/home/stephan/http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] I do want open --keep to be possible with updates
Hello, fossil open myrepo.fossil --keep fossil update ## updates downloads files and they are stored in the current directory. Can't fossil do something like : fossil update --keep # so NO files are written in the current directory ? Best Regards K. ___ 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] I do want open --keep to be possible with updates
'fossil update -n' will just show you what would change if you ran fossil update. 'fossil sync' will just sync the repo and not make any changes but not make any changes to your checkout. Fwiw, I believe update with -n syncs as well. Hth, T On Thursday, February 21, 2013, K. Fossil user wrote: Hello, fossil open myrepo.fossil --keep fossil update ## updates downloads files and they are stored in the current directory. Can't fossil do something like : fossil update --keep # so NO files are written in the current directory ? Best Regards K. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
