refactor state based relaying (fixes update client bug on retries) #435
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* bump sdk version * bump SDK to v0.41.3
colin-axner
commented
Feb 26, 2021
colin-axner
commented
Feb 26, 2021
colin-axner
commented
Feb 26, 2021
* Add swagger setup * Add some routes docs and swagger ui * Add few more route docs * Add swagger docs for remaining routes * Fix golint issues * Fix unused lint issues * check chain-id in AddChain
colin-axner
commented
Mar 8, 2021
colin-axner
changed the title
colin-axner
changed the title
Add a lock to prevent multiple processes from attempting to access the light client database at the same time. This typically resulted in unnecessary errors or even panics
Co-authored-by: Mark <[email protected]>
|
merging into the parent branch as the diffs are hard to read after merging master |
colin-axner
added a commit
that referenced
this pull request
Mar 22, 2021
* refactor connection handshake update messages * refactor channel update msg handling * fix chain id for timeout * fix build * refactor state based relaying (fixes update client bug on retries) (#435) * bump sdk version to v0.41.3 (#430) * bump sdk version * bump SDK to v0.41.3 * inital work for refactoring state based relaying * Modify relayPacketFromSequence * update tendermint client to not prune light blocks (#437) * Address comments and fix lint issues * Fix lint issues * Remove onRtyErr (lint issue) * typo fix (#438) * disable tm pruning (#441) * update release naming (#442) * Implement swagger docs and fix path validation (#434) * Add swagger setup * Add some routes docs and swagger ui * Add few more route docs * Add swagger docs for remaining routes * Fix golint issues * Fix unused lint issues * check chain-id in AddChain * add a light client database lock (#447) Add a lock to prevent multiple processes from attempting to access the light client database at the same time. This typically resulted in unnecessary errors or even panics * Close database connection even if second error triggers (#449) Co-authored-by: Mark <[email protected]> * address comments Co-authored-by: akhilkumarpilli <[email protected]> Co-authored-by: Afanti <[email protected]> Co-authored-by: Akhil Kumar P <[email protected]> Co-authored-by: Mark | Microtick <[email protected]> Co-authored-by: Mark <[email protected]> Co-authored-by: akhilkumarpilli <[email protected]> Co-authored-by: Afanti <[email protected]> Co-authored-by: Akhil Kumar P <[email protected]> Co-authored-by: Mark | Microtick <[email protected]> Co-authored-by: Mark <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.