Tags: ripple/validator-history-service
Tags
Bump @types/node to v20 (#334) ## High Level Overview of Change <!-- Please include a summary/list of the changes. If too broad, please consider splitting into multiple PRs. If a relevant Asana task, please link it here. --> Bump dev dependency @type/node to v20 since we have bumped node version to 20.
fix: remove db access per validation for fee data (#328) ## High Level Overview of Change <!-- Please include a summary/list of the changes. If too broad, please consider splitting into multiple PRs. If a relevant Asana task, please link it here. --> The validator table in database is being queried every time there's a new validation to retrieve fee data, which caused this error: `KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?` We can instead cache this validator-network data and update it every hour to reduce number of queries. ### Type of Change <!-- Please check relevant options, delete irrelevant ones. --> - [x] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Refactor (non-breaking change that only restructures code) - [ ] Tests (You added tests for code that already exists, or your new feature included in this PR) - [ ] Documentation Updates - [ ] Release --------- Co-authored-by: Raj Patel <patelraj22777@gmail.com>
Exponential backoff before WebSocket connection retry (#325) ## High Level Overview of Change This change is being introduced to fix hourly agreement not being updated from xahau-main network. 1. Added exponential backoff before WebSocket connection retries, so that the validator server is not swamped with connection requests and hopefully, our server's ip address is not blocked from any further requests. 2. Removed `connectionsInitialized` check from websockets `close` callback before retrying. Since, as per the current design of the code, if all the connections are not initialized and one of the connection (lets say wss://xahau.network/) closes , it won't be retried until next hour. ### Context of Change To fix connection issue specifically for `wss://xahau.network/` ### Type of Change <!-- Please check relevant options, delete irrelevant ones. --> - [x] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Refactor (non-breaking change that only restructures code) - [ ] Tests (You added tests for code that already exists, or your new feature included in this PR) - [ ] Documentation Updates - [ ] Release ## Before / After <!-- If just refactoring / back-end changes, this can be just an in-English description of the change at a technical level. If a UI change, screenshots should be included. --> ## Test Plan This issue occurs only in production. So, we will deploy this branch on staging and see if the intended fix do not cause any issue. <!-- ## Future Tasks For future tasks related to PR. -->
fix: add unl blob v2 (#304) ## High Level Overview of Change <!-- Please include a summary/list of the changes. If too broad, please consider splitting into multiple PRs. If a relevant Asana task, please link it here. --> UNL v2 was deployed to devnet in the most recent reset. This introduces a field called `blobs_v2` which is an array containing multiple blobs. The VHS needs to be fixed to capture this change. This fix has been deployed to staging: https://stg.validator.history.xpring.dev/v1/network/validators/dev And also could be checked at: https://dev.dev.explorer.xpring.dev/network/validators ### Type of Change <!-- Please check relevant options, delete irrelevant ones. --> - [x] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Refactor (non-breaking change that only restructures code) - [ ] Tests (You added tests for code that already exists, or your new feature included in this PR) - [ ] Documentation Updates - [ ] Release
PreviousNext