1 2017-09-17 03:55:55	0|meshcollider|achow101: does the RPC console window position also need fixing?
  2 2017-09-17 03:56:02	0|meshcollider|(for 11335)
  3 2017-09-17 03:56:09	0|achow101|meshcollider: actually, probably
  4 2017-09-17 03:56:12	0|achow101|let me check
  5 2017-09-17 03:56:53	0|achow101|yup, same thing happens with the rpcconsole window
  6 2017-09-17 03:57:07	0|meshcollider|ok I'll push that and squash them all
  7 2017-09-17 03:57:21	0|achow101|it's position is not being saved for me
  8 2017-09-17 03:58:16	0|meshcollider|just for the RPC window? Or the main window too?
  9 2017-09-17 03:58:24	0|achow101|rpc window
 10 2017-09-17 04:00:21	0|achow101|meshcollider: it's only happening if I have -resetguisettings in my command
 11 2017-09-17 04:03:12	0|meshcollider|If you don't have -resetguisettings, does the RPC console window still not save position though?
 12 2017-09-17 04:03:37	0|meshcollider|Of course it will not save position if you reset the settings, because that flag calls settings.clear(); which clears all QSettings
 13 2017-09-17 04:08:29	0|achow101|meshcollider: no, it saves if -resetguisettings was not in the command
 14 2017-09-17 04:09:00	0|achow101|-resetguisettings should be a one and done thing, so after I start up, I shouldn't have a problem with saving settings
 15 2017-09-17 04:09:51	0|meshcollider|hmm actually yeah that's really weird, it definitely saves the position for me even while running with -resetguisettings
 16 2017-09-17 04:10:46	0|meshcollider|and in the code, the only time it is accessed is at     app.createOptionsModel(gArgs.IsArgSet("-resetguisettings")); which is called from main()
 17 2017-09-17 04:11:09	0|meshcollider|so I have no idea how the behavior you're describing could be happening
 18 2017-09-17 05:12:53	0|Machine_Ex98|hello any idea to resolve gap_limit ??
 19 2017-09-17 05:14:59	0|Machine_Ex98|Only problem is Blockchain Receive API’s 20 address gap limit
 20 2017-09-17 05:14:59	0|Machine_Ex98|We currently offer Bitcoin withdrawals and deposits on our website. Blockchain API is used to handle all operations.
 21 2017-09-17 05:17:03	0|CryptAxe|You don't have to ask on every channel.. And that's a companies API not the API of Bitcoin itself
 22 2017-09-17 05:17:59	0|Machine_Ex98|you talk too much i dont like that
 23 2017-09-17 05:18:11	0|CryptAxe|https://blog.blockchain.com/2016/06/15/receive-payments-api-update-address-gap-limits/#more-9024
 24 2017-09-17 05:18:22	0|CryptAxe|That's too bad.
 25 2017-09-17 05:18:40	0|CryptAxe|There is your answer you can stop spamming every channel
 26 2017-09-17 05:18:40	0|meshcollider|Machine_Ex98: That's offtopic in this channel, this channel is only for bitcoin core development
 27 2017-09-17 05:19:04	0|Machine_Ex98|this not answer its explain lol
 28 2017-09-17 05:19:35	0|meshcollider|Take it to #bitcoin
 29 2017-09-17 05:19:52	0|Machine_Ex98|if 20 people no one of them pay then whats will do ??
 30 2017-09-17 05:20:04	0|luke-jr|Machine_Ex98: and most importantly, *don't* use APIs
 31 2017-09-17 05:20:24	0|Machine_Ex98|Luke-jr whats should use !!
 32 2017-09-17 05:21:29	0|luke-jr|Machine_Ex98: a full node you run yourself in a secure facility.
 33 2017-09-17 05:22:02	0|Machine_Ex98|will its possible to bypass gap limit by making one address btc ??
 34 2017-09-17 05:23:07	0|luke-jr|Machine_Ex98: you won't get any help using web APIs here, and since it is a bad practice, I would hope nowhere.
 35 2017-09-17 05:24:41	0|Machine_Ex98|i dont know whats the point to open irc's server !!
 36 2017-09-17 05:25:17	0|Machine_Ex98|300 bots here without any reason
 37 2017-09-17 05:25:20	0|meshcollider|You'd get more help if you were in the right channel -_-
 38 2017-09-17 05:25:21	0|Machine_Ex98|wtf
 39 2017-09-17 05:25:26	0|luke-jr|meshcollider: hopefully not
 40 2017-09-17 05:25:31	0|luke-jr|Machine_Ex98: what service do you run?
 41 2017-09-17 05:25:35	0|Machine_Ex98|whats this channel for ?
 42 2017-09-17 05:25:46	0|meshcollider|luke-jr: true, I mean help in general, even help running a full node himself
 43 2017-09-17 05:26:21	0|Machine_Ex98|this a shiit irc software
 44 2017-09-17 05:26:54	0|meshcollider|Machine_Ex98: I already told you that this channel is for bitcoin core development, read the channel name and description, go to #bitcoin channel
 45 2017-09-17 05:26:57	0|Machine_Ex98|irc has gone on 2007 ضall the rest (shiit)
 46 2017-09-17 05:27:20	0|luke-jr|Machine_Ex98: what service do you run?
 47 2017-09-17 05:28:24	0|Machine_Ex98|fk you all
 48 2017-09-17 05:31:53	0|gmaxwell|Another satisfied customer. Ding.
 49 2017-09-17 05:55:22	0|gmaxwell|In the future, please make it clear to people that they will get help in the right place. (e.g. by going and offering to help them yourself there, if you can).  Otherwise, the OT response just sounds like a go away.
 50 2017-09-17 05:56:59	0|luke-jr|there is no right place to get help screwing people over by running an incompetent web wallet using blockchain.info's API.. :/
 51 2017-09-17 05:58:04	0|gmaxwell|indeed, but there are better places to be walked through where not to do that. (also, just giving him their support contact information would probably have answered his immediate question.
 52 2017-09-17 13:45:05	0|bitcoin-git|[13bitcoin] 15azuchi opened pull request #11357: Fix description of maximumCount (06master...06fix-0.15.0-release-notes) 02https://github.com/bitcoin/bitcoin/pull/11357
 53 2017-09-17 16:19:56	0|BashCo|0.15 is crashing here on Mac OS 10.9.5 due to segmentation fault. When I use disablewallet=1 it comes up fine. Is this a known issue?
 54 2017-09-17 16:36:49	0|jl2012|BashCo: try removing bitcoin.conf. Should be fine
 55 2017-09-17 16:38:36	0|jl2012|should be related to #11332 . See the transcript of last meeting
 56 2017-09-17 16:38:37	0|gribble|https://github.com/bitcoin/bitcoin/issues/11332 | Fix possible crash with invalid nCustomFeeRadio in QSettings (achow101, TheBlueMatt) by jonasschnelli · Pull Request #11332 · bitcoin/bitcoin · GitHub
 57 2017-09-17 16:44:47	0|achow101|BashCo: can you pastebin the contents of ~/Library/Preferences/bitcoin-qt.plist (or something like that I think)
 58 2017-09-17 16:45:14	0|achow101|BashCo: then start with -resetguisettings
 59 2017-09-17 16:47:22	0|BashCo|removing the bitcoin.conf was the first thing I tried but no luck. my mac os 10.12 system didn't have any issues at all. It's still syncing, then I'll try the older system again. Bet -resetguisettings will fix it.
 60 2017-09-17 16:47:22	0|luke-jr|jl2012: nCustomFeeRadio isn't in bitcoin.conf …
 61 2017-09-17 16:47:55	0|achow101|BashCo: please provide the contents of the file I specified. It has the qsettings info and I want to make sure that that is actually the problem
 62 2017-09-17 16:48:07	0|luke-jr|BashCo: try Knots
 63 2017-09-17 16:48:18	0|luke-jr|also what achow101 said
 64 2017-09-17 16:48:52	0|jl2012|luke-jr: oh, I rarely use the gui. It has another conf?
 65 2017-09-17 16:49:06	0|achow101|jl2012: not another conf, it's the qt settings storage
 66 2017-09-17 16:49:06	0|luke-jr|jl2012: yes, different on every OS
 67 2017-09-17 16:49:24	0|luke-jr|jl2012: on Windows, it's in the registry; on Linux, another ini file somewhere; on Mac, who knows XD
 68 2017-09-17 16:49:54	0|achow101|luke-jr: supposedly on mac it is a plist file at around the location I specified earlier
 69 2017-09-17 16:50:02	0|achow101|(I actually have no idea, that's just what google said)
 70 2017-09-17 16:50:34	0|esotericnonsense|on linux it lives in .config/Bitcoin/Bitcoin-Qt.conf for me
 71 2017-09-17 16:50:34	0|gribble|https://github.com/bitcoin/bitcoin/issues/11082 | Add new bitcoin_rw.conf file that is used for settings modified by this software itself by luke-jr · Pull Request #11082 · bitcoin/bitcoin · GitHub
 72 2017-09-17 16:50:46	0|esotericnonsense|(regardless of datadir settings)
 73 2017-09-17 16:51:12	0|achow101|luke-jr: I don't think that would help since this is a qt specific thing
 74 2017-09-17 16:51:27	0|achow101|unless you mean that we should scrap qsettings altogether and do our own settings stuff
 75 2017-09-17 16:51:41	0|luke-jr|achow101: it's a possibility
 76 2017-09-17 16:52:12	0|luke-jr|haven't given much thought to whether actually-GUI-specific options should be moved there
 77 2017-09-17 17:07:56	0|BashCo|achow101: -resetguisettings worked. Unfortunately I did that before looking for the plist file. :(  I found the file though, called `org.bitcoin.Bitcoin-Qt.plist`.
 78 2017-09-17 17:11:56	0|BashCo|achow101: here's the plist file contents. I probably botched it by using resetguisettings first. https://pastebin.com/Avi6c20Z
 79 2017-09-17 17:16:30	0|achow101|BashCo: yeah, having the file after doing resetguisettings is not particularly helpful
 80 2017-09-17 17:16:39	0|achow101|but at least we know where the file on osx is
 81 2017-09-17 17:16:58	0|BashCo|my bad. sorry about that.
 82 2017-09-17 17:18:29	0|BashCo|achow101: would the crash log be helpful?
 83 2017-09-17 17:18:59	0|achow101|BashCo: yes
 84 2017-09-17 17:19:16	0|achow101|we've already figured out the most probably cause, so this is only to confirm that it's the same problem
 85 2017-09-17 17:20:51	0|BashCo|sent via DM.
 86 2017-09-17 20:21:32	0|esotericnonsense|so i'm investigating #11315 Prune undermines the dbcache
 87 2017-09-17 20:21:33	0|gribble|https://github.com/bitcoin/bitcoin/issues/11315 | Prune undermines the dbcache. · Issue #11315 · bitcoin/bitcoin · GitHub
 88 2017-09-17 20:21:53	0|esotericnonsense|just looking at the code without testing; i don't believe that it's an issue with the prune size
 89 2017-09-17 20:22:13	0|esotericnonsense|fDoFullFlush = (mode == FLUSH_STATE_ALWAYS) || fCacheLarge || fCacheCritical || fPeriodicFlush || fFlushForPrune;
 90 2017-09-17 20:25:17	0|esotericnonsense|unless i'm misinterpreting it seems to imply that any prune event will cause a flush, unless flush just means write in this context?
 91 2017-09-17 20:27:48	0|esotericnonsense|it seems to me that you need to write (because otherwise in the case of an unclean shutdown, you've potentially deleted the blocks you would need to recover) but you don't need to drop the cache entirely
 92 2017-09-17 20:28:42	0|esotericnonsense|ah, perhaps there's only a flush and no way to simply write :)
 93 2017-09-17 20:32:18	0|sipa|yes, there is
 94 2017-09-17 20:32:40	0|sipa|*yes, there is no simple write
 95 2017-09-17 20:33:41	0|sipa|every write to the chainstate requires first writing changes to the block index, to avoid having a chainstate that contains results of blocks that aren't known anymore after restart
 96 2017-09-17 20:35:01	0|esotericnonsense|i think i understand gmax's comment now, you'd let it increase to say prunesize+buffer+dbcache and then prune down (so the interval between prunes is dbcache+buffer rather than buffer)
 97 2017-09-17 20:35:40	0|esotericnonsense|that seems kind of hacky though, it's more like adding a range to prune so that it doesn't go off too often
 98 2017-09-17 20:36:38	0|sipa|right
 99 2017-09-17 20:46:46	0|esotericnonsense|a problem i can see with using dbcache is that if a user has an extremely high value set there could be unexpected results, would need to be documented
100 2017-09-17 20:48:11	0|esotericnonsense|e.g. prune=2000 dbcache=16000, now you can actually use 18GB prior to pruning, hm
101 2017-09-17 20:57:46	0|gmaxwell|esotericnonsense: yes, but we can document it, there are already interactions like that: e.g. the shutdown warning is moved up by the dbcache
102 2017-09-17 20:58:19	0|esotericnonsense|ah, hello. i was just writing a reply on the issue.
103 2017-09-17 20:59:13	0|gmaxwell|IMO ultimately we will end up not having MB tunable pruning. It doesn't really make a lot of sense.
104 2017-09-17 20:59:15	0|esotericnonsense|i was thinking that perhaps using a percentage of the prune as the buffer might work and not require an additional config flag
105 2017-09-17 20:59:55	0|gmaxwell|there shouldn't be an extra setting for sure. please no more options that users can't sensibly configure.
106 2017-09-17 20:59:59	0|esotericnonsense|right now the performance hit is the same regardless of whether you have prune=100000 or prune=1000 (once you get past the point at which it starts doing it)
107 2017-09-17 21:01:19	0|gmaxwell|The point I was trying to make in the issue, I think, is that setting prune shouldn't effectively override your dbcache setting.
108 2017-09-17 21:04:00	0|esotericnonsense|it might be useful for me to get some hard numbers for how much sync time increases depending on the buffer size
109 2017-09-17 21:04:39	0|esotericnonsense|i recall it being 30% slower or more in my testing, but it wasn't very scientific, getting that down to 5% or something would be a pretty big win
110 2017-09-17 21:05:16	0|esotericnonsense|(and that was on SSD)
111 2017-09-17 21:05:51	0|gmaxwell|esotericnonsense: oh jesus no. The difference between a maximum dbcache and default is something like an 8 hour sync vs a 3 hour one.
112 2017-09-17 21:06:59	0|esotericnonsense|yeah, i didn't let it run to the end before increasing the prune target :P
113 2017-09-17 21:07:21	0|esotericnonsense|(i basically did the manual version of this by increasing prune to 50G, then down to 5G, then back up, etc)
114 2017-09-17 21:07:47	0|gmaxwell|esotericnonsense: consider this, right now the chainstate on disk is 2.8gb  adding the dbcache to the interval on syncing with defaults would end up with you needing to have 4GB free to sync bitcoin instead of 3.5.
115 2017-09-17 21:08:08	0|esotericnonsense|gah
116 2017-09-17 21:08:14	0|esotericnonsense|i'm forgetting that if it's in the cache it's not on disk
117 2017-09-17 21:08:18	0|esotericnonsense|heh
118 2017-09-17 21:08:35	0|gmaxwell|potentially at least.
119 2017-09-17 21:08:51	0|esotericnonsense|well, during IBD and in cases where there hasn't been a lot of replacement
120 2017-09-17 21:10:21	0|esotericnonsense|the default dbcache would still result in a lot of prune events flushing it though. hm.
121 2017-09-17 21:10:35	0|esotericnonsense|oh wait it flushes anyway. duh
122 2017-09-17 21:11:00	0|esotericnonsense|okay, that makes sense, i'll play around with it.
123 2017-09-17 22:24:10	0|bitcoin-git|[13bitcoin] 15esotericnonsense opened pull request #11359: Add a pruning 'high water mark' to reduce the frequency of pruning events (06master...062017-09-add-pruning-hwm) 02https://github.com/bitcoin/bitcoin/pull/11359