The blockchain that provides the digital content namespace for the LBRY protocol

bitcoin blockchain c-plus-plus cryptocurrency decentralized lbry

Find a file

MarcoFalke 2c35fe6238 Merge #15849 : Thread names in logs and deadlock debug tools `8722e54e56` threads: add thread names to deadlock debugging message (James O'Beirne) `383b186c28` threads: prefix log messages with thread names (James O'Beirne) `ddd95ccb80` tests: add threadutil tests (James O'Beirne) `ae5f2b6a6c` threads: introduce util/threadnames, refactor thread naming (James O'Beirne) `188ca75e5f` disable HAVE_THREAD_LOCAL on unreliable platforms (James O'Beirne) Pull request description: I'm resurrecting this one (from #13168) because I need it to make progress on #15735. It's now off by default and can be turned on with `-logthreadnames=1`. Ran some benchmarks (IBD from local peer from 500_000 -> 504_000) and it's within spitting distance either on or off: ### threadnames off (default) #### 2018-05-threadnames.3 vs. master (absolute) \| name \| iterations \| 2018-05-threadnames.3 \| master \| \|------------------------------------------------\|-----------:\|----------------------------\|----------------------------\| \| ibd.local.500000.504000.dbcache=2048 \| 3 \| 376.1584 (± 9.2944) \| 392.3414 (± 13.4238) \| \| ibd.local.500000.504000.dbcache=2048.mem-usage \| 3 \| 2236117.3333 (± 1845.9623) \| 2238690.6667 (± 2669.3487) \| #### 2018-05-threadnames.3 vs. master (relative) \| name \| iterations \| 2018-05-threadnames.3 \| master \| \|------------------------------------------------\|-----------:\|----------------------:\|-------:\| \| ibd.local.500000.504000.dbcache=2048 \| 3 \| 1 \| 1.043 \| \| ibd.local.500000.504000.dbcache=2048.mem-usage \| 3 \| 1 \| 1.001 \| ### threadnames on #### 2018-05-threadnames-take-2 vs. master (absolute) \| name \| iterations \| 2018-05-threadnames-take-2 \| master \| \|------------------------------------------------\|-----------:\|----------------------------\|----------------------------\| \| ibd.local.500000.504000.dbcache=2048 \| 3 \| 367.6861 (± 0.3941) \| 364.1667 (± 0.9776) \| \| ibd.local.500000.504000.dbcache=2048.mem-usage \| 3 \| 2238461.3333 (± 3697.8730) \| 2237014.6667 (± 3307.6966) \| #### 2018-05-threadnames-take-2 vs. master (relative) \| name \| iterations \| 2018-05-threadnames-take-2 \| master \| \|------------------------------------------------\|-----------:\|---------------------------:\|-------:\| \| ibd.local.500000.504000.dbcache=2048 \| 3 \| 1.010 \| 1.00 \| \| ibd.local.500000.504000.dbcache=2048.mem-usage \| 3 \| 1.001 \| 1.00 \| ``` ACKs for commit 8722e5: Empact: utACK `8722e54e56` jnewbery: utACK `8722e54e56` MarcoFalke: re-utACK `8722e54e56` (Only change since my previous review is DEFAULT_LOGTHREADNAMES=false and stylistic updates Tree-SHA512: 50af992708295b8d680cf10025262dd964e599a356bdfc1dfc84fb18c00afabcb34d3d12d551b0677ff81f8fccad0e17c1d5b24dfecb953a913bc77fdd1a4577		2019-04-30 15:26:01 -04:00
.github	Get more info about GUI-related issue on Linux	2018-12-27 06:53:07 +02:00
.travis	travis: Switch to ubuntu keyserver to avoid timeouts	2019-03-29 11:38:25 -04:00
.tx	qt: Pre-0.18 split-off translations update	2019-02-04 15:24:37 +01:00
build-aux/m4	Bump minimum Qt version to 5.5.1	2019-02-14 11:12:30 +01:00
build_msvc	Align MSVC build options with Linux build ones	2019-04-27 10:11:52 +03:00
contrib	contrib: gh-merge: Use pagination to fetch all review comments	2019-04-17 20:21:45 +01:00
depends	Merge #15446 : Improve depends debuggability	2019-04-08 10:19:14 -04:00
doc	Merge #15849 : Thread names in logs and deadlock debug tools	2019-04-30 15:26:01 -04:00
share	Merge #15548 : build: use full version string in setup.exe	2019-03-12 10:43:08 +01:00
src	Merge #15849 : Thread names in logs and deadlock debug tools	2019-04-30 15:26:01 -04:00
test	Merge #15696 : [qa] test_runner: Move feature_pruning to base tests	2019-04-30 10:09:54 -04:00
.appveyor.yml	appveyor: Write @PACKAGE_NAME@ to config	2019-04-26 13:07:11 -04:00
.cirrus.yml	cirrus ci: Inital config	2019-02-03 10:24:39 -05:00
.gitattributes	Separate protocol versioning from clientversion	2014-10-29 00:24:40 -04:00
.gitignore	gitignore: add *.plist (clang-check)	2019-04-12 15:25:00 -04:00
.python-version	.python-version: Specify full version 3.5.6	2019-03-02 12:06:26 -05:00
.style.yapf	test: .style.yapf: Set column_limit=160	2019-03-04 18:28:13 -05:00
.travis.yml	travis: Bump second timeout to 33 minutes, Add rationale	2019-04-11 14:56:56 -04:00
autogen.sh	Add "export LC_ALL=C" to all shell scripts	2018-06-14 15:27:52 +02:00
configure.ac	Merge #15849 : Thread names in logs and deadlock debug tools	2019-04-30 15:26:01 -04:00
CONTRIBUTING.md	Doc: update ACK description in CONTRIBUTING.md	2019-03-20 12:10:35 +01:00
COPYING	[Trivial] Update license year range to 2019	2018-12-31 04:27:59 +01:00
INSTALL.md	Update INSTALL landing redirection notice for build instructions.	2016-10-06 12:27:23 +13:00
libbitcoinconsensus.pc.in	Unify package name to as few places as possible without major changes	2015-12-14 02:11:10 +00:00
Makefile.am	Merge #12051 : add missing debian contrib file to tarball	2019-04-29 08:48:39 -04:00
README.md	docs: Update Transifex links	2019-03-02 17:42:33 +08:00

README.md

Bitcoin Core integration/staging tree

https://bitcoincore.org

What is Bitcoin?

Bitcoin is an experimental digital currency that enables instant payments to anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Bitcoin Core is the name of open source software which enables the use of this currency.

For more information, as well as an immediately useable, binary version of the Bitcoin Core software, see https://bitcoincore.org/en/download/, or read the original whitepaper.

License

Bitcoin Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

Development Process

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of Bitcoin Core.

The contribution workflow is described in CONTRIBUTING.md and useful hints for developers can be found in doc/developer-notes.md.

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.

Automated Testing

Developers are strongly encouraged to write unit tests for new code, and to submit new unit tests for old code. Unit tests can be compiled and run (assuming they weren't disabled in configure) with: make check. Further details on running and extending unit tests can be found in /src/test/README.md.

There are also regression and integration tests, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: test/functional/test_runner.py

The Travis CI system makes sure that every pull request is built for Windows, Linux, and macOS, and that unit/sanity tests are run automatically.

Manual Quality Assurance (QA) Testing

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.

Translations

Changes to translations as well as new translations can be submitted to Bitcoin Core's Transifex page.

Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.

Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.

Translators should also subscribe to the mailing list.