< Lico>
Hi guys I am sorry for the basic question, but I would like to debug the bitcoin and I would like to know what tools for debug do you use for Ubuntu ? Does anybody use and IDE for Ubuntu ? I tried to use netbeans, eclipse
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #13706: doc: Minor improvements to release-process.md (master...release_process_doc) https://github.com/bitcoin/bitcoin/pull/13706
< bitcoin-git>
bitcoin/master 94dd89e MarcoFalke: Merge #13706: doc: Minor improvements to release-process.md...
< bitcoin-git>
bitcoin/master 1c22cc1 Mitchell Cash: doc: Update broken links to now point to gitian-build.py
< bitcoin-git>
bitcoin/master 95464c7 Mitchell Cash: doc: Improve command to generate list of authors for release notes...
< bitcoin-git>
[bitcoin] kallewoof closed pull request #10386: [WIP] [wallet] Optional '-avoidreuse' flag which defaults to not reusing addresses in sends (master...feature-white-black-address) https://github.com/bitcoin/bitcoin/pull/10386
< bitbee>
is roger ver still stealing bitcoin core code?
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #13650: [travis] Don't store debug info if --enable-debug is set (master...travis-debug-fix) https://github.com/bitcoin/bitcoin/pull/13650
< bitcoin-git>
bitcoin/master 7a9bca6 MarcoFalke: Merge #13650: [travis] Don't store debug info if --enable-debug is set...
< bitcoin-git>
bitcoin/master 14788fb Chun Kuan Lee: [travis] Don't store debug info if --enable-debug is set
< bitcoin-git>
[bitcoin] kallewoof reopened pull request #10386: [WIP] [wallet] Optional '-avoidreuse' flag which defaults to not reusing addresses in sends (master...feature-white-black-address) https://github.com/bitcoin/bitcoin/pull/10386
< bitcoin-git>
[bitcoin] laanwj closed pull request #12257: [wallet] Use destination groups instead of coins in coin select (master...feature-addrgrouped-coinselect) https://github.com/bitcoin/bitcoin/pull/12257
< bitcoin-git>
[bitcoin] 251Labs opened pull request #13751: Utils and libraries: Drops the boost/algorithm/string/split.hpp dependency (master...patch/remove_boost_split) https://github.com/bitcoin/bitcoin/pull/13751
< bitcoin-git>
[bitcoin] Sjors opened pull request #13750: depends: use MacOS friendly sed syntax in qt.mk (master...2018/07/depends-qt-macos) https://github.com/bitcoin/bitcoin/pull/13750
< ossifrage>
harding, in my case I think it is just that my node has been up for a while and the connection count is wandering up and with it the non-bitcoin nodes (recently lost my old ip address thanks to verizon-quality)
< bitcoin-git>
[bitcoin] domob1812 opened pull request #13747: tests: Skip P2PConnection's is_closing() check when not available (master...skip-isclosing) https://github.com/bitcoin/bitcoin/pull/13747
< wumpus>
no, but in this case, being able to embed comments in JSON wouldn't help, they'd get lost in transit. bitcoin-cli parses and reformats the JSON to add indentation and such to make it more human-readable , which would lose comments
< gmaxwell>
(inspired by someone who looked like they nearly pasted the output of dumpprivkey into #bitcoin)
< gribble>
https://github.com/bitcoin/bitcoin/issues/12257 | [wallet] Use destination groups instead of coins in coin select by kallewoof · Pull Request #12257 · bitcoin/bitcoin · GitHubAsset 1Asset 1
< bitcoin-git>
[bitcoin] DrahtBot reopened pull request #12096: [rpc] [wallet] Allow specifying the output index when using bumpfee (master...better-bumpfee) https://github.com/bitcoin/bitcoin/pull/12096
< bitcoin-git>
[bitcoin] DrahtBot reopened pull request #12676: Show "bip125-replaceable" flag, when retrieving mempool entries (master...rpc-raw-replaceable-flag) https://github.com/bitcoin/bitcoin/pull/12676
< bitcoin-git>
[bitcoin] DrahtBot closed pull request #12911: wallet: Show fee in results for signrawtransaction* when known (master...sign-show-fees) https://github.com/bitcoin/bitcoin/pull/12911
< bitcoin-git>
[bitcoin] DrahtBot closed pull request #13084: Do not turn OP_1NEGATE in scriptSig into 0x0181 in signing code (master...201804_keepnegone) https://github.com/bitcoin/bitcoin/pull/13084
< bitcoin-git>
[bitcoin] DrahtBot closed pull request #13247: Add tests to SingleThreadedSchedulerClient() and document the memory model (master...scheduler-tests) https://github.com/bitcoin/bitcoin/pull/13247
< bitcoin-git>
[bitcoin] fanquake closed pull request #12825: Only allocate a LevelDB block cache if LevelDB will actually use it (master...buffer-cache) https://github.com/bitcoin/bitcoin/pull/12825
< bitcoin-git>
[bitcoin] fanquake opened pull request #13741: Only allocate a LevelDB block cache if LevelDB will actually use it (master...eklitzke-buffer-cache-rebased) https://github.com/bitcoin/bitcoin/pull/13741
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #11762: Avoid locking mutexes that are already held by the same thread (master...remove-double-locks) https://github.com/bitcoin/bitcoin/pull/11762
< bitcoin-git>
bitcoin/master 05714f9 MarcoFalke: Merge #11762: Avoid locking mutexes that are already held by the same thread...
< bitcoin-git>
bitcoin/master 01a06d6 practicalswift: Avoid locking mutexes that are already held by the same thread
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #12764: doc: Remove field in getblocktemplate help that has never been used. (master...remove_unused_gbt_field) https://github.com/bitcoin/bitcoin/pull/12764
< bitcoin-git>
bitcoin/master ac8a1d0 Conor Scott: [RPC] Remove field in getblocktemplate help that has never been used
< bitcoin-git>
bitcoin/master 10b9a81 MarcoFalke: Merge #12764: doc: Remove field in getblocktemplate help that has never been used....
< bitcoin-git>
[bitcoin] DrahtBot closed pull request #12825: Only allocate a LevelDB block cache if LevelDB will actually use it (master...buffer-cache) https://github.com/bitcoin/bitcoin/pull/12825
< bitcoin-git>
[bitcoin] DrahtBot reopened pull request #12984: logs: Make the columns in subsequent UpdateTip log entries horizontally aligned (master...attention-to-detail) https://github.com/bitcoin/bitcoin/pull/12984
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #13729: travis: Avoid unnecessarily setting env variables on the lint build (master...ci-lint-env) https://github.com/bitcoin/bitcoin/pull/13729
< bitcoin-git>
bitcoin/master 515348f Ben Woosley: Don't unnecessarily install shellcheck on the lint build...
< bitcoin-git>
bitcoin/master 751c958 Ben Woosley: Use the Travis python language feature on the lint build...
< bitcoin-git>
bitcoin/master 1be5c33 Ben Woosley: Avoid unnecessarily setting env variables on the lint build...
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #13683: wallet: Introduce assertion to document the assumption that cache and cache_used are always set in tandem (master...null-pointer-dereference) https://github.com/bitcoin/bitcoin/pull/13683
< bitcoin-git>
bitcoin/master e8c7434 MarcoFalke: Merge #13683: wallet: Introduce assertion to document the assumption that cache and cache_used are always set in tandem...
< bitcoin-git>
[bitcoin] DrahtBot closed pull request #12764: Remove field in getblocktemplate help that has never been used. (master...remove_unused_gbt_field) https://github.com/bitcoin/bitcoin/pull/12764
< bitcoin-git>
[bitcoin] AtsukiTak opened pull request #13733: Utils: Refactor ArgsManager a little (master...tiny-refactor-args-manager) https://github.com/bitcoin/bitcoin/pull/13733
< walletissue>
I have big problem with my wallet , I have synced the bitcoin core wallet with blockchain network recently and now I can see transactions in my wallet and I have positive receive transactions but I cant see my btc in my balance or transfer it to other addresses I need urgent help to fic problem.
< fanquake>
I've added a "Mergeable" list to https://github.com/bitcoin/bitcoin/projects/8. It'll be easy to add very close to/mergeable PRs to that, rather than always calling them out here.
< bitcoin-git>
[bitcoin] Empact opened pull request #13729: Scripts and tools: Avoid unnecessarily setting env variables on the lint build (master...ci-lint-env) https://github.com/bitcoin/bitcoin/pull/13729
< bitcoin-git>
[bitcoin] Empact opened pull request #13728: Run the CI lint stage on mac and linux both (master...bsd-bash-compatibility) https://github.com/bitcoin/bitcoin/pull/13728
< bitcoin-git>
[bitcoin] ken2812221 opened pull request #13724: [contrib] Support ARM and RISC-V symbol check (master...symbol-check-all) https://github.com/bitcoin/bitcoin/pull/13724
< bitcoin-git>
[bitcoin] hmel opened pull request #13722: [Trivial] Use variable name instead of relying on class layout (master...use_varname_not_this) https://github.com/bitcoin/bitcoin/pull/13722
< kallewoof>
I'm torn on https://github.com/bitcoin/bitcoin/pull/12257#discussion_r203741762 -- on the one hand, we want to give correct values for ancestor count; on the other hand, the reason ancestor count is taken into account is because we want to avoid too-long chains of unconfirmed transactions, which is separate. on the third (?) hand, the accurate ancestor count will give a hint at the number of ancestors the resulting transaction
< bitcoin-git>
[bitcoin] achow101 opened pull request #13721: Bugfixes for BIP 174 combining and deserialization (master...psbt-fixes) https://github.com/bitcoin/bitcoin/pull/13721
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #13712: wallet: Fix non-determinism in ParseHDKeypath(...). Avoid using an uninitialized variable in path calculation. (master...check-ParseUInt32-return-value) https://github.com/bitcoin/bitcoin/pull/13712
< bitcoin-git>
bitcoin/master 27ee53c practicalswift: wallet: Add error handling. Check return value of ParseUInt32(...) in ParseHDKeypath(...).
< bitcoin-git>
bitcoin/master aba2e66 MarcoFalke: Merge #13712: wallet: Fix non-determinism in ParseHDKeypath(...). Avoid using an uninitialized variable in path calculation....
< bitcoin-git>
bitcoin/master 7223263 practicalswift: wallet: Add tests for ParseHDKeypath(...)
< bitcoin-git>
[bitcoin] practicalswift opened pull request #13720: build: Make lint-locale-dependence.sh work with BSD grep (avoid empty subexpressions) (master...bsd-grep-compatibility) https://github.com/bitcoin/bitcoin/pull/13720
< bitcoin-git>
[bitcoin] sipa opened pull request #13719: Avoid creating a temporary vector for size-prefixed elements (master...201807_psbt_no_vec_serialize) https://github.com/bitcoin/bitcoin/pull/13719
< gmaxwell>
wumpus: right, I think the reason I found the socket most interesting was better security, e.g. making it easy to give a group access to the bitcoin daemon rather than all of localhost.
< gmaxwell>
wumpus: Do we have a way to test it without bitcoin-cli support?
< wumpus>
otherwise I'm not sure this is ever going to happen, though I still think it's useful even without bitcoin-cli support
< cfields>
wumpus: I think that makes sense. They're Bitcoin Core downloads, not Bitcoin downloads. If bitcoin.org wants to mirror them, that's their prerogative.
< luke-jr>
wumpus: I think we should leave that up to bitcoin.org, and encourage them to be multi-fullnode
< wumpus>
provoostenator: so can you connect locally to the 127.0.0.1:port that tor connects on to reach bitcoin?
< wumpus>
so in any case: does everyone think I should stop uploading bitcoin core to bitcoin.org? this would be a complete break with them, maybe that's better than waiting for cobra to decide to no longer support core as he's already threatened at least once, but I'm ambivalent abouti t
< moneyball>
The current thinking is to have it in Tokyo in October after Scaling Bitcoin
< luke-jr>
(and making it harder to "just run bitcoin.org" seems a step in that direction)
< luke-jr>
if people are running/updating Core simply because it's on bitcoin.org, that is kind of a systemic risk we should address if possible
< achow101>
there's ongoing work to move all of the bitcoin core stuff from bitcoin.org to bitcoincore.org
< luke-jr>
Cobra wanted to make Knots the "default" on bitcoin.org a while back; we could encourage that, or (probably better) encourage not having a "default"
< achow101>
wumpus: are you aware of the recent events on bitcoin.org?
< wumpus>
achow101: are you seriously suggesting I should no longer update bitcoin.org and upload binaries there?
< wumpus>
luke-jr: possibly, but at the least it loses the qsettings, that's also why it's not "Bitcoin core" named there yet
< achow101>
as in we should simply take the bitcoin.org steps out of our release process and if someone wants to do them later, then that's fine
< achow101>
I was thinking that it may not be appropriate to make release posts on bitcoin.org, at least not before they go up on bitcoincore.or
< wumpus>
I think the link to bitcoin.org is only for the *general* descriptoin of bitcoin
< luke-jr>
bitcoin.org could increase distance further, but someone needs to do that work, and people whined when they tried, so I think it's stuck
< provoostenator>
And there's guiconstants.h: QAPP_ORG_DOMAIN "bitcoin.org"
< jnewbery>
I don't think we link to bitcoin.org for downloads any more
< achow101>
we still link to bitcoin.org for things like downloads
< wumpus>
#topic moving away from bitcoin.org more (achow101)
< achow101>
topic suggestion: moving away from bitcoin.org more
< jonasschnelli>
No strong opinion... but slighly prefere to have it under the bitcoin-core repository
< lclc>
I know there are several seeder implementations but it appears to be the most used one. And since getting new node IPs by DNS is the default way to bootstrap a node in Core I think it makes sense to have one implementation in the bitcoin-core org.
< luke-jr>
should we put bfgminer, knots, kallewoof's script debugger stuff, etc under bitcoin-core too? :p
< lclc>
I though because there are a few open issues and simple PRs for bitcoin-seeder and it might would make sense that several Bitcoin maintainers have merge rights.
< wumpus>
#topic bitcoin-seeder under bitcoin-core GitHub organisation (lclc)
< bitcoin-git>
[bitcoin] masonicboom opened pull request #13717: docs: Link to python style guidelines from developer notes (master...link-to-python-style-guidelines-from-dev-notes) https://github.com/bitcoin/bitcoin/pull/13717
< gribble>
https://github.com/bitcoin/bitcoin/issues/13712 | wallet: Fix non-determinism in ParseHDKeypath(...). Avoid using an uninitialized variable in path calculation. by practicalswift · Pull Request #13712 · bitcoin/bitcoin · GitHub
< gribble>
https://github.com/bitcoin/bitcoin/issues/13426 | [bugfix] Add u8path and u8string to fix encoding issue for Windows by ken2812221 · Pull Request #13426 · bitcoin/bitcoin · GitHub