https://github.com/tendermint/tendermint

sort by:
Revision Author Date Message Commit Date
ea539dc Update changelog for v0.35.0-rc2. (#7011) Also, relinkify and update the bounty URL. 28 September 2021, 14:59:47 UTC
e35a42f e2e: use smaller transactions (#7016) 75% of the failures in the last run all ran with the 10kb transactions. I'd like to dial it back and see if things improve more. 28 September 2021, 14:39:26 UTC
1bd1593 fix: race condition in p2p_switch and pex_reactor (#7015) Closes https://github.com/tendermint/tendermint/issues/7014 28 September 2021, 13:32:14 UTC
6be3661 e2e: reduce number of stateless nodes in test networks (#7010) 27 September 2021, 21:00:05 UTC
9a16d93 statesync: add logging while waiting for peers (#7007) 27 September 2021, 20:46:40 UTC
8023a2a e2e: add generator tests (#7008) 27 September 2021, 19:38:03 UTC
6eaa3b2 ci: use cheaper codecov data collection (#7009) 27 September 2021, 19:22:25 UTC
b150ea6 e2e: avoid seed nodes when statesyncing (#7006) 27 September 2021, 18:08:08 UTC
b879f71 e2e: reduce log noise (#7004) 27 September 2021, 17:27:08 UTC
bce7c2f build(deps): Bump google.golang.org/grpc from 1.40.0 to 1.41.0 (#7003) 27 September 2021, 15:12:56 UTC
60a6c6f e2e: allow running of single node using the e2e app (#6982) 27 September 2021, 13:43:07 UTC
fb9eaf5 e2e: improve chances of statesyncing success (#7001) This reduces this situation where a node will get stuck block syncing, which seemed to happen a lot in last nights run. 26 September 2021, 16:10:36 UTC
37ca98a e2e: reduce number of statesyncs in test networks (#6999) 25 September 2021, 23:14:38 UTC
c101fa1 e2e: add limit and sort to generator (#6998) I observed a couple of problems with the generator in some recent tests: - there were a couple of hybrid test cases which did not have any legacy nodes (randomness and all.) I change the probability to produce more reliable results. - added options to the generation to be able to add a max (to compliment the earlier min) number of nodes for local testing. - added an option to support reversing the sort order so "more complex" networks were first, as well as tweaked some of the point values. - this refactored the generators cli parsing to be a bit more clear. 25 September 2021, 15:53:04 UTC
118bfe2 abci: Flush socket requests and responses immediately. (#6997) The main effect of this change is to flush the socket client and server message encoding buffers immediately once the message is fully and correctly encoded. This allows us to remove the timer and some other special cases, without changing the observed behaviour of the system. -- Background The socket protocol client and server each use a buffered writer to encode request and response messages onto the underlying connection. This reduces the possibility of a single message being split across multiple writes, but has the side-effect that a request may remain buffered for some time. The implementation worked around this by keeping a ticker that occasionally triggers a flush, and by flushing the writer in response to an explicit request baked into the client/server protocol (see also #6994). These workarounds are both unnecessary: Once a message has been dequeued for sending and fully encoded in wire format, there is no real use keeping all or part of it buffered locally. Moreover, using an asynchronous process to flush the buffer makes the round-trip performance of the request unpredictable. -- Benchmarks Code: https://play.golang.org/p/0ChUOxJOiHt I found no pre-existing performance benchmarks to justify the flush pattern, but a natural question is whether this will significantly harm client/server performance. To test this, I implemented a simple benchmark that transfers randomly-sized byte buffers from a no-op "client" to a no-op "server" over a Unix-domain socket, using a buffered writer, both with and without explicit flushes after each write. As the following data show, flushing every time (FLUSH=true) does reduce raw throughput, but not by a significant amount except for very small request sizes, where the transfer time is already trivial (1.9μs). Given that the client is calibrated for 1MiB transactions, the overhead is not meaningful. The percentage in each section is the speedup for flushing only when the buffer is full, relative to flushing every block. The benchmark uses the default buffer size (4096 bytes), which is the same value used by the socket client and server implementation: FLUSH NBLOCKS MAX AVG TOTAL ELAPSED TIME/BLOCK false 3957471 512 255 1011165416 2.00018873s 505ns true 1068568 512 255 273064368 2.000217051s 1.871µs (73%) false 536096 4096 2048 1098066401 2.000229108s 3.731µs true 477911 4096 2047 978746731 2.000177825s 4.185µs (10.8%) false 124595 16384 8181 1019340160 2.000235086s 16.053µs true 120995 16384 8179 989703064 2.000329349s 16.532µs (2.9%) false 2114 1048576 525693 1111316541 2.000479928s 946.3µs true 2083 1048576 526379 1096449173 2.001817137s 961.025µs (1.5%) Note also that the FLUSH=false baseline is actually faster than the production code, which flushes more often than is required by the buffer filling up. Moreover, the timer slows down the overall transaction rate of the client and server, indepenedent of how fast the socket transfer is, so the loss on a real workload is probably much less. 24 September 2021, 22:37:25 UTC
71c6682 statesync: clean up reactor/syncer lifecylce (#6995) I've been noticing that there are a number of situations where the statesync reactor blocks waiting for peers (or similar,) I've moved things around to improve outcomes in local tests. 24 September 2021, 21:40:12 UTC
dbad701 ci: use smart merges (#6993) 24 September 2021, 18:59:10 UTC
5e45676 e2e: do not inject evidence through light proxy (#6992) In the last run, there were two problems at the RPC layer returned from light nodes' RPC end points. I think exercising the light client proxy RPC system is something that can/should be done via unit testing, and that likely these errors are (in production) transient and (in CI) very likely to fail for test environment issues. 24 September 2021, 18:27:00 UTC
08982c8 e2e: skip validation of status apphash (#6991) I believe this assertion is likely redundant given that we're checking the block apphash. 24 September 2021, 17:49:06 UTC
b203c91 rpc: implement BroadcastTxCommit without event subscriptions (#6984) 24 September 2021, 17:01:35 UTC
ab8cfb9 e2e: tighten timing for load generation (#6990) 24 September 2021, 16:28:51 UTC
c909f8a e2e: avoid non-determinism in app hash check (#6985) 24 September 2021, 15:52:47 UTC
363b87e changelog: add entry for interanlizations (#6989) 24 September 2021, 14:50:19 UTC
dd4141e build(deps): Bump github.com/go-kit/kit from 0.11.0 to 0.12.0 (#6988) Bumps [github.com/go-kit/kit](https://github.com/go-kit/kit) from 0.11.0 to 0.12.0. - [Release notes](https://github.com/go-kit/kit/releases) - [Commits](https://github.com/go-kit/kit/compare/v0.11.0...v0.12.0) --- updated-dependencies: - dependency-name: github.com/go-kit/kit dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> 24 September 2021, 14:15:30 UTC
5ccd668 e2e: load should be proportional to network (#6983) 23 September 2021, 20:58:10 UTC
e94c418 e2e: always preserve failed networks (#6981) 23 September 2021, 18:52:14 UTC
3d410e4 e2e: only check validator sets after statesync (#6980) 23 September 2021, 18:31:59 UTC
8a171b8 e2e: improve manifest sorting algorithim (#6979) 23 September 2021, 16:42:20 UTC
bb8ffcb store: move pacakge to internal (#6978) 23 September 2021, 15:46:42 UTC
cf7537e cleanup: Reduce and normalize import path aliasing. (#6975) The code in the Tendermint repository makes heavy use of import aliasing. This is made necessary by our extensive reuse of common base package names, and by repetition of similar names across different subdirectories. Unfortunately we have not been very consistent about which packages we alias in various circumstances, and the aliases we use vary. In the spirit of the advice in the style guide and https://github.com/golang/go/wiki/CodeReviewComments#imports, his change makes an effort to clean up and normalize import aliasing. This change makes no API or behavioral changes. It is a pure cleanup intended o help make the code more readable to developers (including myself) trying to understand what is being imported where. Only unexported names have been modified, and the changes were generated and applied mechanically with gofmt -r and comby, respecting the lexical and syntactic rules of Go. Even so, I did not fix every inconsistency. Where the changes would be too disruptive, I left it alone. The principles I followed in this cleanup are: - Remove aliases that restate the package name. - Remove aliases where the base package name is unambiguous. - Move overly-terse abbreviations from the import to the usage site. - Fix lexical issues (remove underscores, remove capitalization). - Fix import groupings to more closely match the style guide. - Group blank (side-effecting) imports and ensure they are commented. - Add aliases to multiple imports with the same base package name. 23 September 2021, 14:52:07 UTC
c9beef7 proto: regenerate code (#6977) ## Description Replace all seemed to have been used causing proto files to be changed without being regenerated 23 September 2021, 12:37:11 UTC
41ac5b9 Fix script paths in go:generate directives. (#6973) We moved some files further down in the directory structure in #6964, which caused the relative paths to the mockery wrapper to stop working. There does not seem to be an obvious way to get the module root as a default environment variable, so for now I just added the extra up-slashes. 23 September 2021, 01:02:24 UTC
7e4cc59 Remove the unused rpc/client/mocks package. (#6974) This package is not used in the tendermint repository since 31e7cdee. Note that this is not the same package as rpc/client/mock (N.B. singular) which is still used in some tests. A search of GitHub turns up only 11 uses, all of which are in clones of the tendermint repo at old commits.. 23 September 2021, 00:45:11 UTC
1995ef2 rpc: Strip down the base RPC client interface. (#6971) * rpc: Strip down the base RPC client interface. Prior to this change, the RPC client interface requires implementing the entire Service interface, but most of the methods of Service are not needed by the concrete clients. Dissociate the Client interface from the Service interface. - Extract only those methods of Service that are necessary to make the existing clients work. - Update the clients to combine Start/Onstart and Stop/OnStop. This does not change what the clients do to start or stop. Only the websocket clients make use of this functionality anyway. The websocket implementation uses some plumbing from the BaseService helper. We should be able to excising that entirely, but the current interface dependencies among the clients would require a much larger change, and one that leaks into other (non-RPC) packages. As a less-invasive intermediate step, preserve the existing client behaviour (and tests) by extracting the necessary subset of the BaseService functionality to an analogous RunState helper for clients. I plan to obsolete that type in a future PR, but for now this makes a useful waypoint. Related: - Clean up client implementations. - Update mocks. 22 September 2021, 21:26:35 UTC
d04b6c2 e2e: run multiple should use preserve (#6972) 22 September 2021, 17:13:31 UTC
1c4950d state: move package to internal (#6964) 22 September 2021, 17:04:25 UTC
6383465 ci: reduce number of groups for 0.34 e2e runs (#6968) 22 September 2021, 16:48:38 UTC
07d1018 inspect: remove duplicated construction path (#6966) 22 September 2021, 16:32:49 UTC
5a13c70 rfc: event system (#6957) 21 September 2021, 15:22:55 UTC
0f53a59 readme: update discord links (#6965) This updates the Discord invite links. 21 September 2021, 10:35:40 UTC
df2d744 config/docs: update and deprecated (#6879) ## Description - Add deprecated to config values in toml - update config in configuration doc - explain how to set up a node with the new network - add sentence about not needing to fork tendermint for built-in tutorial - closes #6865 - add note to use a released version of tendermint with the tutorials. This is to avoid unknown issues prior to a release. 21 September 2021, 10:32:00 UTC
84ffaaa statesync/rpc: metrics for the statesync and the rpc SyncInfo (#6795) 21 September 2021, 07:22:16 UTC
9dfdc62 proxy: move proxy package to internal (#6953) 20 September 2021, 19:18:48 UTC
cf59b8b build(deps): Bump github.com/spf13/viper from 1.8.1 to 1.9.0 (#6961) Bumps [github.com/spf13/viper](https://github.com/spf13/viper) from 1.8.1 to 1.9.0. - [Release notes](https://github.com/spf13/viper/releases) - [Commits](https://github.com/spf13/viper/compare/v1.8.1...v1.9.0) --- updated-dependencies: - dependency-name: github.com/spf13/viper dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Sam Kleinman <garen@tychoish.com> 20 September 2021, 17:03:10 UTC
87b876a crypto/armor: remove unused package (#6963) 20 September 2021, 16:30:26 UTC
ad067d7 rfc: Fix a few typos and formatting glitches p2p roadmap (#6960) 20 September 2021, 13:02:29 UTC
ea6eecb build(deps): Bump github.com/vektra/mockery/v2 from 2.9.3 to 2.9.4 (#6956) Bumps [github.com/vektra/mockery/v2](https://github.com/vektra/mockery) from 2.9.3 to 2.9.4. - [Release notes](https://github.com/vektra/mockery/releases) - [Changelog](https://github.com/vektra/mockery/blob/master/.goreleaser.yml) - [Commits](https://github.com/vektra/mockery/compare/v2.9.3...v2.9.4) --- updated-dependencies: - dependency-name: github.com/vektra/mockery/v2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> 17 September 2021, 14:06:40 UTC
bf9232e e2e: cleanup on all errors if preserve not specified (#6950) If the e2e tests error, they leave all of the e2e state around including containers and networks etc. We should clean this up when the tests shuts down, even if it exits in error. 17 September 2021, 08:35:49 UTC
b0423e2 e2e: allow load generator to succed for short tests (#6952) This should address last night's failure. We've taken the perspective of "the load generator shouldn't cause tests to fail" in recent days/weeks, and I think this is just a next step along that line. The e2e tests shouldn't test performance. I included some comments indicating the ways that this isn't ideal (it is perhaps not), and I think that if test networks could make assertions about the required rate, that might be a cool future improvement (and good, perhaps, for system benchmarking.) 16 September 2021, 15:45:51 UTC
b0684bd build(deps): Bump github.com/vektra/mockery/v2 from 2.9.0 to 2.9.3 (#6951) Bumps [github.com/vektra/mockery/v2](https://github.com/vektra/mockery) from 2.9.0 to 2.9.3. - [Release notes](https://github.com/vektra/mockery/releases) - [Changelog](https://github.com/vektra/mockery/blob/master/.goreleaser.yml) - [Commits](https://github.com/vektra/mockery/compare/v2.9.0...v2.9.3) --- updated-dependencies: - dependency-name: github.com/vektra/mockery/v2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> 16 September 2021, 12:41:46 UTC
382947c rfc: add performance taxonomy rfc (#6921) This document attempts to capture and discuss some of the areas of Tendermint that seem to be cited as causing performance issue. I'm hoping to continue to gather feedback and input on this document to better understand what issues Tendermint performance may cause for our users. The overall goal of this document is to allow the maintainers and community to get a better sense of these issues and to be more capably able to discuss them and weight trade-offs about any proposed performance-focused changes. This document does not aim to propose any performance improvements. It does suggest useful places for benchmarks and places where additional metrics would be useful for diagnosing and further understanding Tendermint performance. Please comment with areas where my reasoning seems off or with additional areas that Tendermint performance may be causing user pain. 16 September 2021, 06:13:27 UTC
9a7ce08 statesync: shut down node when statesync fails (#6944) 16 September 2021, 05:43:23 UTC
55f6d20 e2e: skip broadcastTxCommit check (#6949) I think the `Sync` check covers our primary use case, and perhaps we can turn this back on in the future after some kind of event-system rewrite, or RPC rewrite that will avoid the serverside timeout. 15 September 2021, 21:24:35 UTC
b9c35c1 docs: fix openapi yaml lint (#6948) saw this in the super lint. 15 September 2021, 19:29:25 UTC
f08f72e rfc: e2e improvements (#6941) 15 September 2021, 19:26:39 UTC
e932b46 e2e: tweak semantics of waitForHeight (#6943) 15 September 2021, 18:49:24 UTC
5db2a39 docs: add documentation of unsafe_flush_mempool to openapi (#6947) 15 September 2021, 15:28:01 UTC
6909158 e2e: reduce load pressure (#6939) 14 September 2021, 14:44:30 UTC
de2cffe build(deps): Bump codecov/codecov-action from 2.0.3 to 2.1.0 (#6938) 14 September 2021, 12:31:41 UTC
c257cda e2e: slow load processes with longer evidence timeouts (#6936) These are mostly the timeouts that I think we're still hitting in CI. At this point, the tests (on master) pass on my local machine (which is quite beefy) so I think this is just the first in (perhaps?) a sequence of changes that attempt to change timeouts and load patterns so that the tests pass in CI more reliably. 13 September 2021, 20:57:25 UTC
5a49d1b RFC 002 Interprocess Communication in Tendermint (#6913) Communication in Tendermint among consensus nodes, applications, and operator tools all use different message formats and transport mechanisms. In some cases there are multiple options. Having all these options complicates both the code and the developer experience, and hides bugs. To support a more robust, trustworthy, and usable system, we should document which communication paths are essential, which could be removed or reduced in scope, and what we can improve for the most important use cases. This document proposes a variety of possible improvements of varying size and scope. Specific design proposals should get their own documentation. 13 September 2021, 19:41:21 UTC
e4feb56 Update CHANGELOG.md for release v0.34.13. (#6935) Fixes #6933. I forgot to update master after I did the v0.34.13 release. 13 September 2021, 18:58:04 UTC
abbe820 e2e: reduce load volume (#6932) 13 September 2021, 17:45:01 UTC
723bf92 ci: skip coverage tasks for test infrastructure (#6934) 13 September 2021, 17:23:16 UTC
ef79241 ci: skip coverage for non-go changes (#6927) 13 September 2021, 13:06:56 UTC
3bf0c7a e2e: improve p2p mode selection (#6929) The previous implemention of hybrid set testing, which was entirely my own creation, was a bit peculiar, and I think this probably clears thins up. The previous implementation had far fewer legacy nodes in hybrid networks, *and* also for some reason that I can't quite explain, caused a test case to fail. 12 September 2021, 06:30:58 UTC
055f1b3 ci: disable codecov patch status check (#6930) 10 September 2021, 23:08:04 UTC
1998cf7 e2e: compile tests (#6926) 10 September 2021, 17:34:26 UTC
c3bcf9b e2e: test multiple broadcast tx methods (#6925) 10 September 2021, 16:03:41 UTC
f1b9613 e2e: increase retain height to at least twice evidence age (#6924) 10 September 2021, 14:18:01 UTC
5d279c9 build(deps): Bump github.com/rs/zerolog from 1.24.0 to 1.25.0 (#6923) Bumps [github.com/rs/zerolog](https://github.com/rs/zerolog) from 1.24.0 to 1.25.0. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rs/zerolog/commit/65adfd88ecb983005c9f735d207e11d63216ca00"><code>65adfd8</code></a> Make Fields method accept both map and slice (<a href="https://github-redirect.dependabot.com/rs/zerolog/issues/352">#352</a>)</li> <li>See full diff in <a href="https://github.com/rs/zerolog/compare/v1.24.0...v1.25.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=github.com/rs/zerolog&package-manager=go_modules&previous-version=1.24.0&new-version=1.25.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> 10 September 2021, 13:38:55 UTC
af71f1c e2e: load generation and logging changes (#6912) 10 September 2021, 13:26:17 UTC
1a9bad9 ci: tweak code coverage settings (#6920) 09 September 2021, 19:58:52 UTC
db690c3 rpc: fix hash encoding in JSON parameters (#6813) The responses from node RPCs encode hash values as hexadecimal strings. This behaviour is stipulated in our OpenAPI documentation. In some cases, however, hashes received as JSON parameters were being decoded as byte buffers, as is the convention for JSON. This resulted in the confusing situation that a hash reported by one request (e.g., broadcast_tx_commit) could not be passed as a parameter to another (e.g., tx) via JSON, without translating the hex-encoded output hash into the base64 encoding used by JSON for opaque bytes. Fixes #6802. 09 September 2021, 19:51:17 UTC
0c3601b e2e: introduce canonical ordering of manifests (#6918) 09 September 2021, 18:31:17 UTC
816e9b0 ci: drop codecov bot (#6917) 09 September 2021, 18:04:56 UTC
2a224fb rfc: database storage engine (#6897) 09 September 2021, 16:42:15 UTC
2a74c9c update readme to more accurately reflect the tendermint public api (#6916) 08 September 2021, 21:49:36 UTC
dc0e04d rename configuration parameters to use the new blocksync nomenclature (#6896) The 0.35 release cycle renamed the 'fastsync' functionality to 'blocksync'. This change brings the configuration parameters in line with that change. Namely, it updates the configuration file `[fastsync]` field to be `[blocksync]` and changes the command line flag and config file parameters `--fast-sync` and `fast-sync` to `--enable-block-sync` and `enable-block-sync` respectively. Error messages were added to help users encountering these changes be able to quickly make the needed update to their files/scripts. When using the old command line argument for fast-sync, the following is printed ``` ./build/tendermint start --proxy-app=kvstore --consensus.create-empty-blocks=false --fast-sync=false ERROR: invalid argument "false" for "--fast-sync" flag: --fast-sync has been deprecated, please use --enable-block-sync ``` When using one of the old config file parameters, the following is printed: ``` ./build/tendermint start --proxy-app=kvstore --consensus.create-empty-blocks=false ERROR: error in config file: a configuration parameter named 'fast-sync' was found in the configuration file. The 'fast-sync' parameter has been renamed to 'enable-block-sync', please update the 'fast-sync' field in your configuration file to 'enable-block-sync' ``` 08 September 2021, 13:58:12 UTC
63aeb50 upgrading: add information into the UPGRADING.md for users of the codebase wishing to upgrade (#6898) * add information on upgrading to the new p2p library * clarify p2p backwards compatibility * reorder p2p queue list * add demo for p2p selection * fix spacing in upgrading 08 September 2021, 13:41:12 UTC
9b458a1 update changelog ahead of v0.35 release (#6893) This change moves the changelog entries from CHANGELOG_PENDING.md to CHANGELOG.md ahead of the 0.35 release. 07 September 2021, 22:38:45 UTC
cfe64ed cleanup: fix order of linters in the golangci-lint config (#6910) This is a cosmetic change that restores lexicographic order to the selected linters in the CI config. No change to which linters we run, only putting them back in order so it's easier to spot the one you care about. 07 September 2021, 20:08:46 UTC
db6e031 doc: fix a typo in the indexing section (#6909) 07 September 2021, 18:44:23 UTC
04cca01 build(deps): Bump github.com/golangci/golangci-lint (#6907) Bumps [github.com/golangci/golangci-lint](https://github.com/golangci/golangci-lint) from 1.42.0 to 1.42.1. - [Release notes](https://github.com/golangci/golangci-lint/releases) - [Changelog](https://github.com/golangci/golangci-lint/blob/master/CHANGELOG.md) - [Commits](https://github.com/golangci/golangci-lint/compare/v1.42.0...v1.42.1) --- updated-dependencies: - dependency-name: github.com/golangci/golangci-lint dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> 07 September 2021, 12:55:25 UTC
8fe651b e2e: clean up generation of evidence (#6904) 07 September 2021, 10:20:43 UTC
89539d0 networks: update to latest DigitalOcean modules (#6902) 06 September 2021, 16:04:56 UTC
4bab061 build(deps): Bump docker/setup-buildx-action from 1.5.0 to 1.6.0 (#6903) 06 September 2021, 13:07:27 UTC
5ee39f0 network: update terraform config (#6901) 06 September 2021, 09:53:28 UTC
1f8bb74 e2e: skip assertions for stateless nodes (#6894) 03 September 2021, 17:25:36 UTC
77615b9 e2e: wait for all nodes rather than just one (#6892) 03 September 2021, 17:03:16 UTC
21b5e59 e2e: skip light clients when waiting for height (#6891) 03 September 2021, 14:19:15 UTC
0055f9e build(deps): Bump github.com/lib/pq from 1.10.2 to 1.10.3 (#6890) Bumps [github.com/lib/pq](https://github.com/lib/pq) from 1.10.2 to 1.10.3. - [Release notes](https://github.com/lib/pq/releases) - [Commits](https://github.com/lib/pq/compare/v1.10.2...v1.10.3) --- updated-dependencies: - dependency-name: github.com/lib/pq dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> 03 September 2021, 13:07:30 UTC
bda948e statesync: implement p2p state provider (#6807) 02 September 2021, 11:19:18 UTC
511bd3e e2e: weight protocol dimensions (#6884) This changes the focus of the e2e suite, to (roughly) focus on configurations that are more well used. Most production users of tendermint run ABCI application in process and the GRPC/socket methods cover the vast majority of the remaining use cases. Perhaps we should consider drop support unix domain sockets in a future release, but I think in the mean time it's useful to have the tests *mostly* focus on the primary use cases. 01 September 2021, 19:52:40 UTC
9a0081f e2e: change restart mechanism (#6883) 01 September 2021, 16:49:45 UTC
7fe3e78 Update the psql indexer schema and implementation (#6868) Update the schema and implementation of the Postgres event indexer to improve certain types of queries against the index. These changes address the use cases raised by #6843, and are partly inspired by the prototype schema in that issue. In the old schema, events were flattened, making it difficult to find all the events associated with a particular block or transaction. In addition, events with no key/value attributes were entirely lost, since entries were generated only for attributes. To address these issues, this new schema records blocks, transactions, events, and attributes in separate tables, and provides views that join these tables to give a more convenient query surface for block and transaction events. - All events for a given block can be queried from the `block_events` view. - All events for a given transaction can be queried from the `tx_events` view. - Multiple events for the same key can be indexed for both blocks and transactions. The tests have been reworked, but all of the existing test cases for the old schema still pass with the new implementation. Various other minor cleanups are included, ADR-065 is also updated to reflect the updated schema. 31 August 2021, 22:35:07 UTC
7169d26 e2e: more reliable method for selecting node to inject evidence (#6880) In retrospect my previous implementation of this node, could get unlucky and never find the correct node. This method is more reliable. 31 August 2021, 21:56:06 UTC
c4df8a3 types: move mempool error for consistency (#6875) This is a little change just to make things more consistent ahead of the 0.35 release. 30 August 2021, 17:42:58 UTC
f858ebe build(deps): Bump github.com/rs/zerolog from 1.23.0 to 1.24.0 (#6874) Bumps [github.com/rs/zerolog](https://github.com/rs/zerolog) from 1.23.0 to 1.24.0. - [Release notes](https://github.com/rs/zerolog/releases) - [Commits](https://github.com/rs/zerolog/compare/v1.23.0...v1.24.0) --- updated-dependencies: - dependency-name: github.com/rs/zerolog dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> 30 August 2021, 13:34:54 UTC
c9347a0 docs: remove return code in normal case from go built-in example (#6841) An explicit exit prevents the deferred cleanup code from running. In this case, falling off the end of main will achieve the same goal as an explicit exit. 29 August 2021, 16:14:20 UTC
back to top