Merge from dev to main prior to release v0.5.1 #35
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
* Control of max concurrency subroutines, configurable (new env var `MAX_CONCURRENT_TX_PROCESSING` ) * Use version-agnostic events * Add v0.4.0 version tx (v3) * Docker updates to v3 * Ability to start at a particular block, with new env var `BOOTSTRAP_BLOCKHEIGHT` * Better error handling (or error handling at all) * Adding context passing in processTx (TODO apply in all others where applicable) * SQL working from scratch too * minor other stuff * no duplicate key errors locally now, with 5 workers like in the indexer 🤷 ---- * Added unit test TODO: A lot, but this should fix the current state! Tested locally, works fine with 5 workers locally and 32 concurrent routines.
* Fix older binaries for older blocks it was not working with v3 because the binaries were not well specified. (blocks earlier to migration, block `1004550` ) Also it was suboptimal because it had to try first and on failure, run the correct binaries. * Batch reputer requets * Fix forecasts insertion! it was inserting inferences twice. * Batches inserts in rewards and scores. Prepares the ground for networklosses too.
type was not parsed , wrong key. this made rewards were only inserted the first one, with an empty type
Insert raw events in batch
- Add new event handlers for research monitoring - Update tx processor to work against chain v0.5.0
Remove ref to testnet-1.testnet , change to testnet
changelog for 0.5.0
Create sql scripts for upgrade
Merge-back after conflict resolution
We need to create tables for topic `reward` and `forecast task score` to store all histories
* Add height to uniqueness constraint on `ema_scores`, so that the history of ema_scores per actor is kept. --------- Co-authored-by: Kenny <[email protected]>
* Create indexes per topic_id into the tables that have it. --------- Co-authored-by: Kenny <[email protected]>
RedBird96
approved these changes
Sep 25, 2024
Added migration for removal of extra columns on topic
* Insertion of forecasts fixes * Allow for separate insertion of inferences of forecasts if coming separately * Insertion of ema_scores fixed * updates of last_commit_values fixed
Add PR template
kpeluso
approved these changes
Sep 26, 2024
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.
Merge from dev to main prior to release v0.5.1