tendermint

291 MiB

Tree: 540aea1030

Author	SHA1	Message	Date
dependabot[bot]	22b0b67c63	build(deps): Bump github.com/adlio/schema from 1.1.15 to 1.2.2 (#7422 ) * build(deps): Bump github.com/adlio/schema from 1.1.15 to 1.2.2 Bumps [github.com/adlio/schema](https://github.com/adlio/schema) from 1.1.15 to 1.2.2. - [Release notes](https://github.com/adlio/schema/releases) - [Commits](https://github.com/adlio/schema/compare/v1.1.15...v1.2.2) --- updated-dependencies: - dependency-name: github.com/adlio/schema dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> * Work around API changes in the migrator package. A recent update inadvertently broke the API by changing the receiver types of the methods without updating the constructor. See: https://github.com/adlio/schema/issues/13 Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: M. J. Fromberger <fromberger@interchain.io>	3 years ago
mergify[bot]	657afc7322	Remove now-unused nolint:lll directives. (backport #7356 ) (#7358 ) (cherry picked from commit `76dea94a01`) Co-authored-by: M. J. Fromberger <fromberger@interchain.io>	3 years ago
mergify[bot]	260f4250b0	Fix incorrect tests using the PSQL sink. (backport #7349 ) (#7355 ) Some of our tests were creating a psql event sink and expecting it to report (or not report) certain kinds of errors. These tests were ill-founded in a couple of ways: 1. Tests that required the Postgres driver were not loading it. This led to spurious successes on tests that wanted "some error" from the sink constructor, but didn't exercise the right path. 2. Tests that wanted a Postgres sink to succeed without a database. These tests "passed" because they weren't actually establishing a connection to the database, but if they had would have failed for the lack of one. To fix this: - Load the postgres driver in tests that need it. - Verify connectivity before reporting successful creation of a PSQL event sink. - Remove tests that wanted a psql sink without a database, since that case is already tested elsewhere. (cherry picked from commit `ab1788b922`)	3 years ago
M. J. Fromberger	1c1ce83e2d	Performance improvements for the event query API (#7338 ) A manual backport of #7319 and #7336.	3 years ago
M. J. Fromberger	cf7537ea5f	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.	3 years ago
Sam Kleinman	1c4950dbd2	state: move package to internal (#6964 )	3 years ago

6 Commits (540aea1030c7cabf4b710da5f6d323d8dfa00654)