[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] Two bugs
From: |
Neil Conway |
Subject: |
Re: [Monotone-devel] Two bugs |
Date: |
Tue, 16 Nov 2004 22:51:23 +1100 |
User-agent: |
Mozilla Thunderbird 0.9 (Macintosh/20041103) |
Nathaniel Smith wrote:
Two bugs in the 0.15 release that are fixed in the current public
netsync server head for the branch net.venge.monotone.changesets
Thanks!
BTW, I get the following when I try to pull from off.net:
$ monotone --db=mt_pgsql.db --key="" --debug pull off.net net.venge.monotone
[ ... ]
monotone: processing 542602 byte input buffer from peer off.net
monotone: received 'refine' netcmd on rcert node '9e03', level 3
monotone: db.fetch("SELECT COUNT(*) FROM merkle_nodes WHERE type =
'rcert' AND collection = 'net.venge.monotone' AND level = 3 AND prefix =
'9e03' ")
monotone: found corresponding rcert merkle node for prefix '9e03', level 3
monotone: db.fetch("SELECT body FROM merkle_nodes WHERE type = 'rcert'
AND collection = 'net.venge.monotone' AND level = 3 AND prefix = '9e03'")
monotone: (#5) they have a live leaf at slot 0 in rcert node '9e03',
level 3, we have nothing
monotone: queueing request for data of rcert item
'9e0349ba7acbe5e5f4e9e75c626f1560b7aad480'
monotone: (#1) they have an empty slot 1 in rcert node '9e03', level 3,
and so do we
monotone: (#2) they have an empty slot 2 in rcert node '9e03', level 3,
we have a live leaf
monotone: db.fetch("SELECT id FROM revision_certs WHERE hash =
'902033e9ea6d5a925fec1e7c6e534128f18a5e14'")
monotone: db.fetch("SELECT id, name, value, keypair, signature FROM
revision_certs WHERE hash = '902033e9ea6d5a925fec1e7c6e534128f18a5e14'")
monotone: not queueing rcert data for
'902033e9ea6d5a925fec1e7c6e534128f18a5e14' as we are in pure sink role
monotone: (#1) they have an empty slot 3 in rcert node '9e03', level 3,
and so do we
monotone: (#1) they have an empty slot 4 in rcert node '9e03', level 3,
and so do we
monotone: (#1) they have an empty slot 5 in rcert node '9e03', level 3,
and so do we
monotone: (#1) they have an empty slot 6 in rcert node '9e03', level 3,
and so do we
monotone: (#2) they have an empty slot 7 in rcert node '9e03', level 3,
we have a live leaf
monotone: db.fetch("SELECT id FROM revision_certs WHERE hash =
'90707169da0850d0aac317855df20240f113b3c0'")
monotone: warning: caught bad_decode exception processing peer off.net:
'rcert '90707169da0850d0aac317855df20240f113b3c0' does not exist in our
database'
monotone: terminated exchange with off.net
monotone: [bytes in: 866903] [bytes out: 62655]
monotone: db.execute("COMMIT")
$ monotone --db=mt_pgsql.db --branch=net.venge.monotone.changesets heads
monotone: branch 'net.venge.monotone.changesets' is currently unmerged:
5d68bc44d129447862a6ff4982df1dcd4ac2465e address@hidden
2004-11-05T09:47:33
9061dc82b2e87998bdfdec24865ad289c8aa59b7 address@hidden
2004-11-09T04:13:04
This is with a database that was initialized with 0.14, then converted
to the 0.15 format (via migrate and changesetify) -- I initially pulled
the net.venge.monotone collection with 0.14. When I pull from off.net
into a fresh database (created with 0.15), it seems to work:
$ monotone --db=mt_off.db --branch=net.venge.monotone.changesets heads
monotone: branch 'net.venge.monotone.changesets' is currently unmerged:
631e8f001ec1a7b21f8ff379a6c88e7fae394982 address@hidden 2004-11-13T08:55:29
ff75963993cdecc61d7b78f5e90cb13a3c0ce3e7 address@hidden
2004-11-09T04:13:04
-Neil