summaryrefslogtreecommitdiff
path: root/e9/e2d8507a1cd4ef6509e666e3630a5406038f61
blob: 71a32653fe278b54a3b6656a782dc1d9046607b6 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gubatron@gmail.com>) id 1WQKH9-0003QT-Fe
	for bitcoin-development@lists.sourceforge.net;
	Wed, 19 Mar 2014 17:27:35 +0000
Received-SPF: pass (sog-mx-3.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-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WQKH8-0007e3-Jw
	for bitcoin-development@lists.sourceforge.net;
	Wed, 19 Mar 2014 17:27:35 +0000
Received: by mail-qa0-f46.google.com with SMTP id i13so8729279qae.5
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 19 Mar 2014 10:27:29 -0700 (PDT)
X-Received: by 10.224.137.5 with SMTP id u5mr45310546qat.12.1395250049053;
	Wed, 19 Mar 2014 10:27:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.90.105 with HTTP; Wed, 19 Mar 2014 10:27:08 -0700 (PDT)
From: Angel Leon <gubatron@gmail.com>
Date: Wed, 19 Mar 2014 13:27:08 -0400
Message-ID: <CADZB0_aSpu7v0bVV6Po0RonobGVreWTLN7Mya687PbP2t_-oZg@mail.gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=001a11c286048c19d404f4f8f7c9
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: 1WQKH8-0007e3-Jw
Subject: [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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 19 Mar 2014 17:27:35 -0000

--001a11c286048c19d404f4f8f7c9
Content-Type: text/plain; charset=ISO-8859-1

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?

Cheers,
Angel

http://twitter.com/gubatron

--001a11c286048c19d404f4f8f7c9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">the command line options mention a -checklevel =A0paramete=
r.<br>I&#39;ve been passing 0 assuming there&#39;d be little to no verifica=
tion, but it&#39;s happened a few times that when I open the official binar=
y (while not doing development) there&#39;s some sort of database corruptio=
n and Bitcoin-Qt needs to reindex blocks on disk, a process that can take p=
robably a whole day.<br>

<br>how do you guys develop the UI and avoid these issues?<br><br>Cheers,<b=
r>Angel<br><br clear=3D"all"><div><a href=3D"http://twitter.com/gubatron" t=
arget=3D"_blank">http://twitter.com/gubatron</a><br></div>
</div>

--001a11c286048c19d404f4f8f7c9--