Re: [fossil-users] rebuild scale-ability/data written/repo size ratio

[Nikita Borodikhin]

Hi Karel,

as i understand this option, it is indeed for extra integrity checking.  It
checks all the files in your checkout, not only those involved in the
commit and allows to find data corruption on file system.

As other scms don't do that check (svn and git), I think it is safe to
leave it off.

Nikita.


On Sat, Oct 29, 2016, 13:34 Karel Gardas  wrote:

> Hi Nikita,
>
> your advice indeed helped a lot and brings commit to 20 seconds here.
> Now, the question is if I may really leave file integrity to
> file-system or if even ZFS/Btrfs is not enough here and fossil does
> some other magic?
>
> Thanks!
> Karel
>
> On Fri, Oct 28, 2016 at 7:33 PM, Nikita Borodikhin 
> wrote:
> > Hi Karel,
> >
> > I have quite a big repository (3.4G) imported from svn by a custom
> tool.  It
> > also took several minutes to commit, and most of the time was spent in
> md5
> > hash computation.  It is extra precaution to ensure checkout file
> integrity,
> > which can be turned off with repo-cksum setting.
> >
> > With that setting off, it takes 4 to 6 second to commit.
> ___
> 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] visual studio 2015 project for fossil

[Artur Shepilko]

BTW, in general you may use VisualStudio debugger directly without a
solution, by manually starting the 'devenv' as:

  devenv /debugexe fossil.exe

This launches VisualStudio in Debug mode and allows you to 'Step Into' a
new instance of the exe (fossil.exe). By default it breaks in main().

To actually see the source-code in the debugger editor window, fossil.exe
has to be built in DEBUG mode.

  cd win
  buildmsvc DEBUG=1
  cd ..\msvcbld
  devenv /debugexe fossil.exe

Otherwise you have to really be fluent in assembler :)

Once in VS debugger, you can use all of the usual features: call-stack,
break-points, watches, etc.

Of course a solution would give you also source-referencing freedom, but if
you know the source well and not averse to step-debbuging, this gives you
ability to debug projects in the absence of an all-embracing solition, say
CMake based projects etc, or indeed compex projects like fossil that
involves a lot of code-generation.

Hope this helps.


On Sat, Oct 29, 2016 at 12:00 PM, arnoldemu <
mem...@arnoldemu.freeserve.co.uk> wrote:

> Hi,
>
> I have attached a zip file which contains a solution and project file for
> fossil to be used with visual studio 2015 community edition.
>
> This uses nmake to build the project file in the windows directory and it
> will output to the msvcbld directory and generate a executable that you can
> debug in the debugger if you wish.
>
> The build, rebuild and clean menu options in visual studio can be used.
> You can also place a breakpoint in the debugger and launch the debugger and
> it will hit.
>
> Extract the contents of the zip file within the win directory.
>
> I did attempt to make a windows 64-bit build but the following things held
> me back:
> 1. the fossil.exe.manifest in win needs a x64 equivalent. I managed to
> change the makefile to use this but was unable to verify my changes were
> correct. (I put a new fossil.exe.manifest in a sub-directory, and changed
> x86 to x64 in the new file.)
>
> 2. the makefile attempted to link against the win32 version of zlib. I
> wasn't sure how to make it build zlib for x64 so I didn't proceed furthur.
> (without this it will not link correctly).
>
> I hope others may find this useful.
>
> Thanks
>
> Kevin
>
>
>
>
> ___
> 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] unable to revert fossil mv

[Steve Stefanovich]

This is an excellent example of a confusing mv command and a bad default 
choice, as encountered by someone presumably new to Fossil.

The problem is that Fossil doesn't move files on its own, by default. Why would 
anyone want that behaviour, especially as a default, is beyond me.

You need to specify --hard and to have an executable that has been compiled 
with such an option. Search for Joe Mistachin's response to my question about 
it on the mailing list for details.


Cheers,
Steve‎
  Original Message
From: arnoldemu
Sent: Saturday, 29 October 2016 23:45
To: fossil-users@lists.fossil-scm.org
Reply To: Fossil SCM user's discussion
Subject: Re: [fossil-users] unable to revert fossil mv


Update:

I am seeing this:

kevin@kevin:~/arnold/test/disc$ fossil changes
MISSING disk_sizes/data.dsk
MISSING disk_sizes/data2sides.dsk
MISSING disk_sizes/ramdosd1.dsk
MISSING disk_sizes/system.dsk
MISSING disk_sizes/system42.dsk
MISSING disk_sizes/system80t1s.dsk
MISSING disk_sizes/test.dsk
MISSING disk_sizes/vortex.dsk


if I do touch to make these missing files and then do a revert.

Fossil shows me

kevin@kevin:~/arnold/test/disc/disk_sizes$ fossil revert
DELETE test/disc/disk_sizes/data.dsk
DELETE test/disc/disk_sizes/data2sides.dsk
DELETE test/disc/disk_sizes/ramdosd1.dsk
DELETE test/disc/disk_sizes/system.dsk
DELETE test/disc/disk_sizes/system42.dsk
DELETE test/disc/disk_sizes/system80t1s.dsk
DELETE test/disc/disk_sizes/test.dsk
DELETE test/disc/disk_sizes/vortex.dsk
REVERT test/disk_sizes/data.dsk
REVERT test/disk_sizes/data2sides.dsk
REVERT test/disk_sizes/ramdosd1.dsk
REVERT test/disk_sizes/system.dsk
REVERT test/disk_sizes/system42.dsk
REVERT test/disk_sizes/system80t1s.dsk
REVERT test/disk_sizes/test.dsk
REVERT test/disk_sizes/vortex.dsk
"fossil undo" is available to undo changes to the working checkout.

and then:

kevin@kevin:~/arnold/test/disc/disk_sizes$ fossil changes
kevin@kevin:~/arnold/test/disc/disk_sizes$ cd ..

i try again:

kevin@kevin:~/arnold/test$ fossil mv disk_sizes disc/disk_sizes
RENAME test/disk_sizes/data.dsk test/disc/disk_sizes/data.dsk
RENAME test/disk_sizes/data2sides.dsk test/disc/disk_sizes/data2sides.dsk
RENAME test/disk_sizes/ramdosd1.dsk test/disc/disk_sizes/ramdosd1.dsk
RENAME test/disk_sizes/system.dsk test/disc/disk_sizes/system.dsk
RENAME test/disk_sizes/system42.dsk test/disc/disk_sizes/system42.dsk
RENAME test/disk_sizes/system80t1s.dsk test/disc/disk_sizes/system80t1s.dsk
RENAME test/disk_sizes/test.dsk test/disc/disk_sizes/test.dsk
RENAME test/disk_sizes/vortex.dsk test/disc/disk_sizes/vortex.dsk

kevin@kevin:~/arnold/test$ fossil changes
MISSING disc/disk_sizes/data.dsk
MISSING disc/disk_sizes/data2sides.dsk
MISSING disc/disk_sizes/ramdosd1.dsk
MISSING disc/disk_sizes/system.dsk
MISSING disc/disk_sizes/system42.dsk
MISSING disc/disk_sizes/system80t1s.dsk
MISSING disc/disk_sizes/test.dsk
MISSING disc/disk_sizes/vortex.dsk

:(

No way to recover :(



___
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] rebuild scale-ability/data written/repo size ratio

[Karel Gardas]

Hi Nikita,

your advice indeed helped a lot and brings commit to 20 seconds here.
Now, the question is if I may really leave file integrity to
file-system or if even ZFS/Btrfs is not enough here and fossil does
some other magic?

Thanks!
Karel

On Fri, Oct 28, 2016 at 7:33 PM, Nikita Borodikhin  wrote:
> Hi Karel,
>
> I have quite a big repository (3.4G) imported from svn by a custom tool.  It
> also took several minutes to commit, and most of the time was spent in md5
> hash computation.  It is extra precaution to ensure checkout file integrity,
> which can be turned off with repo-cksum setting.
>
> With that setting off, it takes 4 to 6 second to commit.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] windows build patch to use vs2015 static analysis

[arnoldemu]

Hi,

Here is a patch that sets the /analyze compiler switch which enables the vs2015 
static analysis output. I have tested it with vs2015 community edition and the 
latest source distribution of fossil 1.36.

START

--- C:/Users/kev/Downloads/fossil-src-1.361/fossil-1.36/win/Makefile.msc    Mon 
Oct 24 15:59:33 2016
+++ C:/Users/kev/Downloads/fossil-src-1.36/fossil-1.36/win/Makefile.msc    Sat 
Oct 29 14:26:46 2016
@@ -34,6 +34,11 @@
 DEBUG = 0
 !endif
 
+# Enable analysis?
+!ifndef ANALYZE
+ANALYZE = 0
+!endif
+
 # Build the OpenSSL libraries?
 !ifndef FOSSIL_BUILD_SSL
 FOSSIL_BUILD_SSL = 0
@@ -241,6 +246,10 @@
 LDFLAGS   = $(LDFLAGS) /DEBUG
 !else
 CFLAGS    = $(CFLAGS) $(CRTFLAGS) /O2
+!endif
+
+!if $(ANALYZE)!=0
+CFLAGS    = $(CFLAGS) /analyze
 !endif
 
 BCC   = $(CC) $(CFLAGS)

END

use it like this:

buildmsvc ANALYZE=1


The piped output is too large to attach here.

I think it's worth checking these. My experience with other projects has shown 
that sometimes it's a bit over sensitive but it has also found some real 
problems.

A few lines taken from the output:

c:\users\kev\downloads\fossil-src-1.36\fossil-1.36\src\timeline.c(762) : 
warning C6297: Arithmetic overflow:  32-bit value is shifted, then cast to 
64-bit value.  Results might not be an expected value.

c:\users\kev\downloads\fossil-src-1.36\fossil-1.36\src\allrepo.c(323) : warning 
C6246: Local declaration of 'rc' hides declaration of the same name in outer 
scope. For additional information, see previous declaration at line '178' of 
'c:\users\kev\downloads\fossil-src-1.36\fossil-1.36\src\allrepo.c'.: Lines: 178

c:\users\kev\downloads\fossil-src-1.36\fossil-1.36\src\delta.c(465) : warning 
C6385: Reading invalid data from 'collide':  the readable size is 
'_Old_5`nHash*sizeof(int)' bytes, but '8' bytes may be read.: Lines: 350, 351, 
352, 353, 354, 355, 356, 360, 361, 367, 380, 381, 382, 383, 384, 385, 386, 387, 
388, 385, 386, 387, 388, 385, 394, 395, 396, 397, 398, 399, 400, 401, 402, 403, 
405, 407, 408, 424, 425, 426, 427, 431, 432, 433, 434, 435, 437, 441, 444, 447, 
448, 449, 454, 455, 465

c:\users\kev\downloads\fossil-src-1.36\fossil-1.36\src\dispatch.c(505) : 
warning C6011: Dereferencing NULL pointer 'z'. : Lines: 448, 449, 450, 451, 
452, 453, 454, 464, 468, 472, 476, 480, 481, 485, 486, 488, 489, 494, 500, 501, 
502, 505

Best Wishes,
Kevin___
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] unable to revert fossil mv

[arnoldemu]

Update:

I am seeing this:

kevin@kevin:~/arnold/test/disc$ fossil changes
MISSING disk_sizes/data.dsk
MISSING disk_sizes/data2sides.dsk
MISSING disk_sizes/ramdosd1.dsk
MISSING disk_sizes/system.dsk
MISSING disk_sizes/system42.dsk
MISSING disk_sizes/system80t1s.dsk
MISSING disk_sizes/test.dsk
MISSING disk_sizes/vortex.dsk


if I do touch to make these missing files and then do a revert.

Fossil shows me

kevin@kevin:~/arnold/test/disc/disk_sizes$ fossil revert
DELETE test/disc/disk_sizes/data.dsk
DELETE test/disc/disk_sizes/data2sides.dsk
DELETE test/disc/disk_sizes/ramdosd1.dsk
DELETE test/disc/disk_sizes/system.dsk
DELETE test/disc/disk_sizes/system42.dsk
DELETE test/disc/disk_sizes/system80t1s.dsk
DELETE test/disc/disk_sizes/test.dsk
DELETE test/disc/disk_sizes/vortex.dsk
REVERT test/disk_sizes/data.dsk
REVERT test/disk_sizes/data2sides.dsk
REVERT test/disk_sizes/ramdosd1.dsk
REVERT test/disk_sizes/system.dsk
REVERT test/disk_sizes/system42.dsk
REVERT test/disk_sizes/system80t1s.dsk
REVERT test/disk_sizes/test.dsk
REVERT test/disk_sizes/vortex.dsk
"fossil undo" is available to undo changes to the working checkout.

and then:

kevin@kevin:~/arnold/test/disc/disk_sizes$ fossil changes
kevin@kevin:~/arnold/test/disc/disk_sizes$ cd ..

i try again:

kevin@kevin:~/arnold/test$ fossil mv disk_sizes disc/disk_sizes
RENAME test/disk_sizes/data.dsk test/disc/disk_sizes/data.dsk
RENAME test/disk_sizes/data2sides.dsk test/disc/disk_sizes/data2sides.dsk
RENAME test/disk_sizes/ramdosd1.dsk test/disc/disk_sizes/ramdosd1.dsk
RENAME test/disk_sizes/system.dsk test/disc/disk_sizes/system.dsk
RENAME test/disk_sizes/system42.dsk test/disc/disk_sizes/system42.dsk
RENAME test/disk_sizes/system80t1s.dsk test/disc/disk_sizes/system80t1s.dsk
RENAME test/disk_sizes/test.dsk test/disc/disk_sizes/test.dsk
RENAME test/disk_sizes/vortex.dsk test/disc/disk_sizes/vortex.dsk

kevin@kevin:~/arnold/test$ fossil changes
MISSING disc/disk_sizes/data.dsk
MISSING disc/disk_sizes/data2sides.dsk
MISSING disc/disk_sizes/ramdosd1.dsk
MISSING disc/disk_sizes/system.dsk
MISSING disc/disk_sizes/system42.dsk
MISSING disc/disk_sizes/system80t1s.dsk
MISSING disc/disk_sizes/test.dsk
MISSING disc/disk_sizes/vortex.dsk

:(

No way to recover :(



___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] unable to revert fossil mv

[arnoldemu]

Hi,

I have a directory called test

it contains a directory called disc and a directory called disk_sizes.
test/disk_sizes contains a few files with extension "dsk".

I wanted to do this move:

test/disk_sizes -> test/disc/disk_sizes

I worked around the other problem I reported by creating test/disc/disk_sizes.

but I typed:

fossil mv test/disk_sizes test/disc

this moved all files in test/disk_sizes to test/disc. (test/disc is now filled 
with files with extension dsk).

I realised my mistake.

I did:

fossil revert test/disc/*.dsk

fossil reported the UNMANAGE.

i then did "fossil changes".

fossil then listed each file with dsk extension with "MISSING".

I can't revert the change.

i tried to do the mv again and fossil did nothing :(

(I don't know if this is important but I had other files and directories in my 
fossil changes at the same time).

How can I fix this?

I tried to do the move again (but correct this time) and although fossil 
reported it had renamed the files and to the correct location, fossil changes 
didn't have those changes and had the same MISSING. I can't revert and I can 
repeat the operation. :(


Thanks

Kevin




___
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] unexpected result with fossil mv on a directory

[arnoldemu]

LOL one more try:

test/drivetest exists and has files.

test/disc/drivetest or test/disc doesn't exist.


___
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] unexpected result with fossil mv on a directory

[arnoldemu]

Hi,

I re-read my message back and realised I may have caused confusion:

disc/drivetest exists - it is the directory with files I want to move, but when 
I say when neither "disc" or "drivetest" exists, I meant "test/disc" and 
"test/disc/drivetest" sorry if I caused confusion.

Thanks

Kevin



___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] unexpected result with fossil mv on a directory

[arnoldemu]

Hi,

I think I may have found a bug with fossil mv related to moving directories.

I am using fossil version 1.35 3aa86af6aa 2016-06-14 11:10:39 UTC.

I wanted to use fossil mv to move a directory tree.

The tree looks like this:

test/drivetest and I wanted to move it to test/disc/drivetest

If I use:

cd test
fossil mv drivetest disc/drivetest

if disc, drivetest or neither exist on my machine then the move doesn't work as 
I expected.

fossil reports:

RENAME test/drivetest test/disc/drivetest

then "fossil changes" lists nothing.

if both disc and drivetest exist then fossil reports RENAME for every file as I 
expected and fossil submit works as expected.

Is this by design or is it a bug?

Thanks

Kevin





___
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] sites inaccessible

[K. Fossil user]

Hi,
Yesterday I've noticed that Fossil was down for a long time...drh said one day 
that inetd stopped : may be it was the case yesterday ?  
Best Regards

K.

  De : jungle Boogie 
 À : General Discussion of SQLite Database 
; Fossil SCM user's discussion 
 
 Envoyé le : Samedi 29 octobre 2016 7h28
 Objet : [fossil-users] sites inaccessible
   
Hi Dr. Hipp,

Probably a low concern for you at 1:30am your time but I can't connect
to fossil-scm.org or sqlite.org over port 80.

$ curl http://sqlite.org/
curl: (7) Failed to connect to sqlite.org port 80: Connection refused

$ curl http://fossil-scm.org
curl: (7) Failed to connect to fossil-scm.org port 80: Connection refused


https does work:
$ curl https://www.fossil-scm.org

Redirect to Location:
https://www.fossil-scm.org/index.html/doc/trunk/www/index.wiki




$ curl https://www.sqlite.org
http://www.w3.org/TR/html4/strict.dtd;>




SQLite Home Page





-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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] Synchronizing endless loop

[Florian Balmer]

Hello

I have just discovered a situation where Fossil seems to enter an
endless loop when synchronizing a lot of commit data and some
unversioned files. I'm not sure about the exact size limit, but
probably large enough to trigger multiple round-trips.

Steps to reproduce:

Server
==

FreeBSD 9.1-RELEASE amd64
Fossil version 1.36 [c24373934d] 2016-10-24 14:59:33 UTC
Compiled on Oct 25 2016 14:06:50 using clang-3.4.1
(tags/RELEASE_34/dot1-final 208032) (64-bit)

* Create a new empty fossil repository on the server (I named it `test-repo')

Client
==

Windows XP SP3 (32-bit) and Windows 7 SP1 (32-bit)
Fossil version 1.36 [c24373934d] 2016-10-24 14:59:33 UTC
Compiled on Oct 24 2016 13:12:30 using mingw32-3.18-gcc-4.5.0 (32-bit)

* Clone the repository from the server to the client
* Add and commit a lot of files (try the Fossil /src directory)
* Add an unversioned file (I named it `home.wiki')
* Run `fossil sync -u'

Client Output
=

[Password prompt ...]

Sync with http://some.fossil.server/fossil.cgi/test-repo
Round-trips: 2   Artifacts sent: 3  received: 0
Error: bad command: uvigot home.wiki 1477722315
ecb1c59ef204582770184dfc6ddc3f7451224c94 416

Round-trips: 3   Artifacts sent: 3  received: 0
server says: bad command: uvigot home.wiki 1477722315
ecb1c59ef204582770184dfc6ddc3f7451224c94 416

Round-trips: 4   Artifacts sent: 4  received: 0
server says: bad command: uvigot home.wiki 1477722315
ecb1c59ef204582770184dfc6ddc3f7451224c94 416

Round-trips: 5   Artifacts sent: 5  received: 0
server says: bad command: uvigot home.wiki 1477722315
ecb1c59ef204582770184dfc6ddc3f7451224c94 416

Round-trips: 6   Artifacts sent: 6  received: 0
server says: bad command: uvigot home.wiki 1477722315
ecb1c59ef204582770184dfc6ddc3f7451224c94 416

[...]

The displayed hash is the checksum of the unversioned file (verified
with a separate sha1 utility).

Shutting down Fossil at this point does not seem to cause any harm to
the local or remote repository, and the problem can be worked around
by running `fossil sync' first, and then `fossil sync -u' in a second
step, so I would consider this to be only a minor issue.

--Florian
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users