Re: [fossil-users] DB corruption and error msg string mis-handling.

2015-06-23 Thread bch
Thanks Joerg. I'll re-sync shortly. Did you happen to test if it had any of
the 0 byte blobs I had before (and the 1 I still have)?

-bch
On Jun 23, 2015 2:43 AM, Joerg Sonnenberger jo...@britannica.bec.de
wrote:

 On Mon, Jun 22, 2015 at 01:44:12PM -0700, bch wrote:
  W/ latest fossil from tip of [trunk], a pull now looks roughly like
  this (note, no reported errors or warnings, no looping like before,
  but still not actually working properly):

 Well, I've rebuild the repository, so it should have no artifacts like
 before.

 Joerg
 ___
 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] DB corruption and error msg string mis-handling.

2015-06-23 Thread Joerg Sonnenberger
On Tue, Jun 23, 2015 at 08:32:13AM -0700, bch wrote:
 Thanks Joerg. I'll re-sync shortly. Did you happen to test if it had any of
 the 0 byte blobs I had before (and the 1 I still have)?

Likely. As I said, I don't really know why it sometimes creates those :(

Joerg
___
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] DB corruption and error msg string mis-handling.

2015-06-23 Thread bch
Still no dice:

kamloops$ fossil pull --verbose
Pull from http://netbsd.sonnenberger.org
Bytes  Cards  Artifacts Deltas
Sent:9546202  0  0
Received:  78  2  0  0
Pull done, sent: 5082  received: 333  ip: 135.28.13.11
kamloops$

On 6/23/15, Joerg Sonnenberger jo...@britannica.bec.de wrote:
 On Tue, Jun 23, 2015 at 08:32:13AM -0700, bch wrote:
 Thanks Joerg. I'll re-sync shortly. Did you happen to test if it had any
 of
 the 0 byte blobs I had before (and the 1 I still have)?

 Likely. As I said, I don't really know why it sometimes creates those :(

 Joerg
 ___
 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] DB corruption and error msg string mis-handling.

2015-06-23 Thread bch
Good idea (I presume you mean sqltrace):

kamloops$ fossil pull --sqltrace
-- sqlite3_open: [/home/bch/work/netbsd_src/.fslckout]
PRAGMA foreign_keys=OFF;
SELECT sql FROM main.sqlite_master WHERE name=='vfile';
-- sqlite3_open: [/home/bch/.fossil]
PRAGMA foreign_keys=OFF;
SELECT value FROM vvar WHERE name='repository';
ATTACH DATABASE '/home/bch/work/netbsd_src/../fossils/netbsd_src.fsl'
AS 'repository';
SELECT value FROM config WHERE name='allow-symlinks';
SELECT value FROM global_config WHERE name='allow-symlinks';
SELECT value FROM config WHERE name='aux-schema';
SELECT value FROM config WHERE name='auto-shun';
SELECT value FROM global_config WHERE name='auto-shun';
SELECT value FROM config WHERE name='last-sync-url';
SELECT value FROM config WHERE name='last-sync-pw';
SELECT value FROM global_config WHERE name='last-sync-pw';
SELECT value FROM config WHERE name='http-auth:http://netbsd.sonnenberger.org';
SELECT value FROM global_config WHERE
name='http-auth:http://netbsd.sonnenberger.org';
BEGIN;
REPLACE INTO config(name,value,mtime)
VALUES('last-sync-url','http://netbsd.sonnenberger.org',now());
COMMIT;
SELECT value FROM vvar WHERE name='default-user';
SELECT value FROM config WHERE name='default-user';
SELECT value FROM global_config WHERE name='default-user';
SELECT uid FROM user WHERE login='bch';
Pull from http://netbsd.sonnenberger.org

[...]

SELECT value FROM config WHERE name='server-code';
SELECT value FROM config WHERE name='project-code';
SELECT value FROM config WHERE name='dont-push';
SELECT value FROM global_config WHERE name='dont-push';
SELECT value FROM config WHERE name='max-upload';
SELECT value FROM global_config WHERE name='max-upload';
BEGIN;
SELECT value FROM config WHERE name='case-sensitive';
SELECT value FROM global_config WHERE name='case-sensitive';
DELETE FROM global_config WHERE name  =
'repo:/home/bch/work/fossils/netbsd_src.fsl';
INSERT OR IGNORE INTO
global_config(name,value)VALUES('repo:/home/bch/work/fossils/netbsd_src.fsl',1);
DELETE FROM global_config WHERE name  = 'ckout:/home/bch/work/netbsd_src/';
REPLACE INTO global_config(name,
value)VALUES('ckout:/home/bch/work/netbsd_src/','/home/bch/work/fossils/netbsd_src.fsl');
CREATE TEMP TABLE onremote(rid INTEGER PRIMARY KEY);
CREATE TEMP TABLE pending_tkt(uuid TEXT UNIQUE);
CREATE TEMP TABLE time_fudge(  mid INTEGER PRIMARY KEY,  m1 REAL,  cid
INTEGER,  m2 REAL);
SELECT value FROM config WHERE name='cookie';
SELECT value FROM global_config WHERE name='cookie';
SELECT uuid FROM phantom CROSS JOIN blob USING(rid) /*scan*/ WHERE NOT
EXISTS(SELECT 1 FROM shun WHERE uuid=blob.uuid)AND NOT
EXISTS(SELECT 1 FROM private WHERE rid=blob.rid);
SELECT hex(randomblob(20));
SELECT julianday('now');ts sent: 0  received: 0
SELECT rid FROM blob WHERE uuid='e3d2fefd88f1e0ce8f74fe79666e1cea4b54911e';
DELETE FROM private WHERE rid=2138325;
INSERT OR IGNORE INTO onremote VALUES(2138325);
SELECT julianday('2015-06-23T18:55:04') - 2457197.286120012;
DROP TABLE onremote;ifacts sent: 0  received: 0
SELECT value FROM config WHERE name='xfer-common-script';
SELECT value FROM global_config WHERE name='xfer-common-script';
SELECT value FROM config WHERE name='xfer-ticket-script';
SELECT value FROM global_config WHERE name='xfer-ticket-script';
SELECT uuid FROM pending_tkt;
DROP TABLE pending_tkt;
UPDATE time_fudge SET m1=m2-2.89351851851852e-07 WHERE m1=m2 AND
m1m2+2.31481481481481e-05;
SELECT 1 FROM time_fudge;
DROP TABLE time_fudge;
DELETE FROM config WHERE name  = 'ckout:/home/bch/work/netbsd_src/';
REPLACE INTO 
config(name,value,mtime)VALUES('ckout:/home/bch/work/netbsd_src/',1,now());
COMMIT;

Pull done, sent: 5081  received: 333  ip: 135.28.13.11
-- LOOKASIDE_USED 14 77
-- LOOKASIDE_HIT   1457
-- LOOKASIDE_MISS_SIZE  363
-- LOOKASIDE_MISS_FULL0
-- CACHE_USED1134608
-- SCHEMA_USED 34024
-- STMT_USED   0
-- MEMORY_USED   13990161415616
-- MALLOC_SIZE65784
-- MALLOC_COUNT  803846
-- PCACHE_OVFLOW 12154481215448
-- prepared statements59
PRAGMA main.freelist_count;
PRAGMA main.page_count;


On 6/23/15, Joerg Sonnenberger jo...@britannica.bec.de wrote:
 On Tue, Jun 23, 2015 at 11:33:31AM -0700, bch wrote:
 Still no dice:

 kamloops$ fossil pull --verbose
 Pull from http://netbsd.sonnenberger.org
 Bytes  Cards  Artifacts Deltas
 Sent:9546202  0  0
 Received:  78  2  0  0
 Pull done, sent: 5082  received: 333  ip: 135.28.13.11
 kamloops$

 Hm. I wonder if the problem is that your system is asking for artefacts
 that no longer exist my public copy and doesn't loop when it doesn't get
 an answer for any of those. --trace would help for that.

 Joerg
 ___
 fossil-users mailing 

Re: [fossil-users] DB corruption and error msg string mis-handling.

2015-06-23 Thread Joerg Sonnenberger
On Tue, Jun 23, 2015 at 11:33:31AM -0700, bch wrote:
 Still no dice:
 
 kamloops$ fossil pull --verbose
 Pull from http://netbsd.sonnenberger.org
 Bytes  Cards  Artifacts Deltas
 Sent:9546202  0  0
 Received:  78  2  0  0
 Pull done, sent: 5082  received: 333  ip: 135.28.13.11
 kamloops$

Hm. I wonder if the problem is that your system is asking for artefacts
that no longer exist my public copy and doesn't loop when it doesn't get
an answer for any of those. --trace would help for that.

Joerg
___
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] DB corruption and error msg string mis-handling.

2015-06-23 Thread Joerg Sonnenberger
On Tue, Jun 23, 2015 at 01:05:00PM -0600, Andy Bradford wrote:
 Thus said bch on Tue, 23 Jun 2015 11:58:35 -0700:
 
  Good idea (I presume you mean sqltrace):
 
 More likely he meant --httptrace which will reveal the HTTP transactions
 during the pull operation (e.g. what was sent/received).

Yeah, --httptrace.

Joerg
___
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] DB corruption and error msg string mis-handling.

2015-06-23 Thread bch
I tried that (and sent response that only went to Andy (which I think
is not first time has happened between Andy, fossil-users, and
myself)).


kamloops$ fossil pull --httptrace
Pull from http://netbsd.sonnenberger.org
Round-trips: 1   Artifacts sent: 0  received: 0
Pull done, sent: 9759  received: 331  ip: 135.28.13.11
kamloops$


But even on a repo that does pull artifacts, I get no extra output:

kamloops$ fossil pull --httptrace
Pull from http://pkgsrc.sonnenberger.org
Round-trips: 3   Artifacts sent: 0  received: 117
Pull done, sent: 6543  received: 65534  ip: 135.28.13.11
kamloops$


What am I missing ?

-bch


On 6/23/15, Joerg Sonnenberger jo...@britannica.bec.de wrote:
 On Tue, Jun 23, 2015 at 01:05:00PM -0600, Andy Bradford wrote:
 Thus said bch on Tue, 23 Jun 2015 11:58:35 -0700:

  Good idea (I presume you mean sqltrace):

 More likely he meant --httptrace which will reveal the HTTP transactions
 during the pull operation (e.g. what was sent/received).

 Yeah, --httptrace.

 Joerg
 ___
 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] DB corruption and error msg string mis-handling.

2015-06-23 Thread Andy Bradford
Thus said bch on Tue, 23 Jun 2015 11:58:35 -0700:

 Good idea (I presume you mean sqltrace):

More likely he meant --httptrace which will reveal the HTTP transactions
during the pull operation (e.g. what was sent/received).

Andy
--
TAI64 timestamp: 40005589adfe
___
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] DB corruption and error msg string mis-handling.

2015-06-23 Thread Joerg Sonnenberger
On Tue, Jun 23, 2015 at 12:31:20PM -0700, bch wrote:
 I tried that (and sent response that only went to Andy (which I think
 is not first time has happened between Andy, fossil-users, and
 myself)).
 
 
 kamloops$ fossil pull --httptrace
 Pull from http://netbsd.sonnenberger.org
 Round-trips: 1   Artifacts sent: 0  received: 0
 Pull done, sent: 9759  received: 331  ip: 135.28.13.11
 kamloops$
 
 
 But even on a repo that does pull artifacts, I get no extra output:
 
 kamloops$ fossil pull --httptrace
 Pull from http://pkgsrc.sonnenberger.org
 Round-trips: 3   Artifacts sent: 0  received: 117
 Pull done, sent: 6543  received: 65534  ip: 135.28.13.11
 kamloops$
 
 
 What am I missing ?

There should be a trace file for teach round trip.

Joerg
___
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] DB corruption and error msg string mis-handling.

2015-06-23 Thread Joerg Sonnenberger
On Mon, Jun 22, 2015 at 01:44:12PM -0700, bch wrote:
 W/ latest fossil from tip of [trunk], a pull now looks roughly like
 this (note, no reported errors or warnings, no looping like before,
 but still not actually working properly):

Well, I've rebuild the repository, so it should have no artifacts like
before.

Joerg
___
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] DB corruption and error msg string mis-handling.

2015-06-22 Thread bch
W/ latest fossil from tip of [trunk], a pull now looks roughly like
this (note, no reported errors or warnings, no looping like before,
but still not actually working properly):

kamloops$ fossil pull --verbose
Pull from http://netbsd.sonnenberger.org
Bytes  Cards  Artifacts Deltas
Sent:9546202  0  0
Received:1412 31  0  0
Pull done, sent: 5076  received: 1031  ip: 135.28.13.11
kamloops$ fossil timel
=== 2015-06-04 ===
16:11:48 [84f521116f] *CURRENT* Whitespace and macro fixes. (user: wiz
tags: trunk)
16:01:09 [ea0e467f7e] Document the options as a list instead of
embedded text. (user: christos tags: trunk)
09:45:43 [53ab9b8bbe] Ticket 822. (user: msaitoh tags: netbsd-7)
09:44:57 [04f6adcaf6] Pull up following revision(s) (requested by
hsuenaga in ticket #822): sys/net/if_gif.c: revision 1.85
sys/net/if_gif.c: revision 1.86 Obtain softnet_lock before entering IP
networking
 stack from gif software interrupt. Include sys/socketvar.h
for softnet_lock. (user: msaitoh tags: netbsd-7)
09:20:12 [e24f89baf3] Whitespace fixes. (user: wiz tags: trunk)
09:19:59 [6c6ebdc911] Pull out route lookups from L2 output routines
Route lookups for routes of RTF_GATEWAY were done in L2 output
routines such as ether_output, but they should be done in L3 i.e.,
before
 L2 output routines. This change places the lookups between L3
output routines (say ip_output) and the L2 output routines. The change
is based on dyoung's patch submitted in the thread: https://mail-
 index.netbsd.org/tech-net/2013/02/01/msg003847.html You can
find out detailed investigations by dyoung about the issue in there.
Note that the change introduces a workaround for MPLS. ether_output
 knew that it needs to fill the ethertype of a frame as MPLS,
based on a tag of an original route (rtentry), but now we don't pass
it to ehter_output. So we have to tell that in another way. We use
 mtag to do so for now, which introduces some overhead. We
should fix it somehow in the future. Discussed on tech-kern and
tech-net. (user: ozaki-r tags: trunk)
[...]


On 6/19/15, bch brad.har...@gmail.com wrote:
 include fossil-users@ ...

 -- Forwarded message --
 From: bch brad.har...@gmail.com
 Date: Fri, 19 Jun 2015 12:05:13 -0700
 Subject: Re: [fossil-users] DB corruption and error msg string
 mis-handling.
 To: Andy Bradford amb-fos...@bradfords.org

 Hi.

 I got around to reviewing this, and found a couple interesting things:

 1) some of the reported 0-byte entries are now gone

 2) Here is report from the single remaining offender:

 rid: size calculated_size_of_blob, reported_uuid, calculated_sha1
 ==
 1355: 0 calculated_realsize(12),
 reported_uuid(da39a3ee5e6b4b0d3255bfef95601890afd80709),
 calcuated_sha(b844a4567c46013e52dc15a63bda87b7160266ef)

 On 6/11/15, Andy Bradford amb-fos...@bradfords.org wrote:
 Thus said bch on Mon, 08 Jun 2015 15:31:31 -0700:

 rid: size
 ==

 What are some of the SHA1 hashes for these RIDs?

 Thanks,

 Andy
 --
 TAI64 timestamp: 40005579f382




___
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] DB corruption and error msg string mis-handling.

2015-06-11 Thread Andy Bradford
Thus said bch on Mon, 08 Jun 2015 15:31:31 -0700:

 rid: size
 ==

What are some of the SHA1 hashes for these RIDs?

Thanks,

Andy
-- 
TAI64 timestamp: 40005579f382


___
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] DB corruption and error msg string mis-handling.

2015-06-10 Thread bch
So... what do these 0-byte blobs _mean_ ?

I just took the time and rebuilt the repo and retried a pull, but same
problem (content does not match sha1 hash). Does anybody know what a
next step ought to be ?

-bch


On 6/8/15, bch brad.har...@gmail.com wrote:
 rid: size
 ==

 1355: 0
 2090601: 0
 2090613: 0
 2090654: 0
 2090685: 0
 2090719: 0
 2090744: 0
 2090748: 0
 2090762: 0
 2090769: 0
 2090789: 0
 2090811: 0
 2090821: 0
 2090833: 0
 2090840: 0
 2090845: 0
 2090891: 0
 2090903: 0
 2090918: 0
 2090923: 0
 2090948: 0
 2090964: 0
 2090989: 0
 2091012: 0
 2091035: 0
 2091110: 0
 2091128: 0
 2091240: 0
 2091264: 0
 2091288: 0
 2091297: 0
 2091333: 0
 2091339: 0
 2091361: 0
 2091411: 0
 2091427: 0
 2091429: 0
 2091432: 0
 2091463: 0


 On 6/8/15, Joerg Sonnenberger jo...@britannica.bec.de wrote:
 On Mon, Jun 08, 2015 at 02:07:36PM -0700, bch wrote:
 unclear what I should check -- you mean measure blob sizes in the
 sqlite db, or tcpdump or some fossil option w/ another pull attempt

 Right, the entry in the blob table.

 Joerg
 ___
 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] DB corruption and error msg string mis-handling.

2015-06-08 Thread bch
ref: line 196 ./src/xfer.c

...
  sha1sum_blob(content, hash);
  if( !blob_eq_str(pXfer-aToken[1], blob_str(hash), -1) ){
blob_appendf(pXfer-err, content does not match sha1 hash);
  }
...

On 6/8/15, bch brad.har...@gmail.com wrote:
 There's either a corrupted database or transport corruption occurring
 w/ netbsd-src, but additionally apparent string mis-handling in the
 fossil binary:


 kamloops$ fossil pull
 Pull from http://netbsd.sonnenberger.org
 via proxy: http://one.proxy.att.com:8080
 Round-trips: 3   Artifacts sent: 0  received: 12
 content does not match sha1 hash
 Round-trips: 4   Artifacts sent: 0  received: 13
 content does not match sha1 hashcontent does not match sha1 hash
 Round-trips: 5   Artifacts sent: 0  received: 14
 content does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hash
 Round-trips: 6   Artifacts sent: 0  received: 15
 content does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1 hash
 Round-trips: 7   Artifacts sent: 0  received: 16
 content does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hash
 Round-trips: 8   Artifacts sent: 0  received: 17
 content does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1 hash
 Round-trips: 9   Artifacts sent: 0  received: 18
 content does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hash
 Round-trips: 10   Artifacts sent: 0  received: 19
 content does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1 hash
 Round-trips: 11   Artifacts sent: 0  received: 20
 content does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hash
 Round-trips: 12   Artifacts sent: 0  received: 21
 content does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1 hash
 Round-trips: 13   Artifacts sent: 0  received: 22
 content does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hash
 Round-trips: 14   Artifacts sent: 0  received: 23
 content does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1
 hashcontent does not match sha1 hashcontent does not match sha1 hash



 -bch

___
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] DB corruption and error msg string mis-handling.

2015-06-08 Thread Joerg Sonnenberger
On Mon, Jun 08, 2015 at 02:07:36PM -0700, bch wrote:
 unclear what I should check -- you mean measure blob sizes in the
 sqlite db, or tcpdump or some fossil option w/ another pull attempt

Right, the entry in the blob table.

Joerg
___
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] DB corruption and error msg string mis-handling.

2015-06-08 Thread bch
rid: size
==

1355: 0
2090601: 0
2090613: 0
2090654: 0
2090685: 0
2090719: 0
2090744: 0
2090748: 0
2090762: 0
2090769: 0
2090789: 0
2090811: 0
2090821: 0
2090833: 0
2090840: 0
2090845: 0
2090891: 0
2090903: 0
2090918: 0
2090923: 0
2090948: 0
2090964: 0
2090989: 0
2091012: 0
2091035: 0
2091110: 0
2091128: 0
2091240: 0
2091264: 0
2091288: 0
2091297: 0
2091333: 0
2091339: 0
2091361: 0
2091411: 0
2091427: 0
2091429: 0
2091432: 0
2091463: 0


On 6/8/15, Joerg Sonnenberger jo...@britannica.bec.de wrote:
 On Mon, Jun 08, 2015 at 02:07:36PM -0700, bch wrote:
 unclear what I should check -- you mean measure blob sizes in the
 sqlite db, or tcpdump or some fossil option w/ another pull attempt

 Right, the entry in the blob table.

 Joerg
 ___
 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] DB corruption and error msg string mis-handling.

2015-06-08 Thread Joerg Sonnenberger
On Mon, Jun 08, 2015 at 11:52:20AM -0700, bch wrote:
 There's either a corrupted database or transport corruption occurring
 w/ netbsd-src, but additionally apparent string mis-handling in the
 fossil binary:

For unknown reasons, sometimes empty artefacts appear. Can you check
your repo copy?

Joerg
___
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] DB corruption and error msg string mis-handling.

2015-06-08 Thread bch
unclear what I should check -- you mean measure blob sizes in the
sqlite db, or tcpdump or some fossil option w/ another pull attempt
?

-bch


On 6/8/15, Joerg Sonnenberger jo...@britannica.bec.de wrote:
 On Mon, Jun 08, 2015 at 11:52:20AM -0700, bch wrote:
 There's either a corrupted database or transport corruption occurring
 w/ netbsd-src, but additionally apparent string mis-handling in the
 fossil binary:

 For unknown reasons, sometimes empty artefacts appear. Can you check
 your repo copy?

 Joerg
 ___
 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