Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WQLMK-0005J8-85 for bitcoin-development@lists.sourceforge.net; Wed, 19 Mar 2014 18:37:00 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.46 as permitted sender) client-ip=209.85.216.46; envelope-from=gubatron@gmail.com; helo=mail-qa0-f46.google.com; Received: from mail-qa0-f46.google.com ([209.85.216.46]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WQLMG-0003h0-Q2 for bitcoin-development@lists.sourceforge.net; Wed, 19 Mar 2014 18:37:00 +0000 Received: by mail-qa0-f46.google.com with SMTP id i13so9058540qae.33 for ; Wed, 19 Mar 2014 11:36:51 -0700 (PDT) X-Received: by 10.229.221.1 with SMTP id ia1mr10160713qcb.6.1395254211294; Wed, 19 Mar 2014 11:36:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.90.105 with HTTP; Wed, 19 Mar 2014 11:36:31 -0700 (PDT) In-Reply-To: References: From: Angel Leon Date: Wed, 19 Mar 2014 14:36:31 -0400 Message-ID: To: Wladimir Content-Type: multipart/alternative; boundary=001a11344280a2bf6f04f4f9ef0a X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gubatron[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WQLMG-0003h0-Q2 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] [QT] how to disable block verification for faster UI testing? X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Mar 2014 18:37:00 -0000 --001a11344280a2bf6f04f4f9ef0a Content-Type: text/plain; charset=ISO-8859-1 "If you have database problems are you perhaps switching between 0.8.x and 0.9.x with the same directory?" I think that may have been the issue. Maybe now that I have a 0.9.0 official binary, when I switch to the source builds I won't have the issue. However, I think I'll do what you do and have separate bitcoin data directories, that's probably the best. not trying to test anything specifically, just codign, building, launching over and over, would like to make the startup of the Qt client faster. http://twitter.com/gubatron On Wed, Mar 19, 2014 at 2:22 PM, Wladimir wrote: > > On Wed, Mar 19, 2014 at 6:27 PM, Angel Leon wrote: > >> the command line options mention a -checklevel parameter. >> I've been passing 0 assuming there'd be little to no verification, but >> it's happened a few times that when I open the official binary (while not >> doing development) there's some sort of database corruption and Bitcoin-Qt >> needs to reindex blocks on disk, a process that can take probably a whole >> day. >> >> how do you guys develop the UI and avoid these issues? >> > > In general I do very little with the database while developing the UI. I > have various seperate bitcoin data directories (both testnet and mainnet) > to try things out. Before doing something risky I just make a copy. > > These days I also do a lot of development with -regtest, as it allows > quickly setting up test scenarios. > > What are you trying to test specifically? The progress bar while > reindexing? > > If you have database problems are you perhaps switching between 0.8.x and > 0.9.x with the same directory? In that case see the downgrading warning > here: https://bitcoin.org/bin/0.9.0/README.txt . > > Wladimir > > --001a11344280a2bf6f04f4f9ef0a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
"If you have database problems are you perhaps switching between 0.8= .x and 0.9.x with the same directory?"
I think that may have been t= he issue.

Maybe now that I have a 0.9.0 official binary, when I switch to the sou= rce builds I won't have the issue.

However, I think I'll do = what you do and have separate bitcoin data directories, that's probably= the best.

not trying to test anything specifically, just codign, building, launch= ing over and over, would like to make the startup of the Qt client faster.<= /span>



On Wed, Mar 19, 2014 at 2:22 PM, Wladimi= r <laanwj@gmail.com> wrote:

=
On Wed, Mar 19, 2014 at 6:27 PM, Angel Leon <gubat= ron@gmail.com> wrote:
the comm= and line options mention a -checklevel =A0parameter.
I've been passi= ng 0 assuming there'd be little to no verification, but it's happen= ed a few times that when I open the official binary (while not doing develo= pment) there's some sort of database corruption and Bitcoin-Qt needs to= reindex blocks on disk, a process that can take probably a whole day.

how do you guys develop the UI and avoid these issues?

In general I do very little with the = database while developing the UI. I have various seperate bitcoin data dire= ctories (both testnet and mainnet) to try things out. Before doing somethin= g risky I just make a copy.

These days I also do a lot of development with -regtest, as = it allows quickly setting up test scenarios.

W= hat are you trying to test specifically? The progress bar while reindexing?=

If you have database problems are you perhaps switching betw= een 0.8.x and 0.9.x with the same directory? In that case see the downgradi= ng warning here: https://bitcoin.org/bin/0.9.0/README.txt .
Wladimir


--001a11344280a2bf6f04f4f9ef0a--