Release v0.21.2
#371
Merged
Release v0.21.2
#371
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
Bets class objects will now also tracking the amount being invested.
invested amount during update should be added instead of updating the new value
the new variable name signifies that it is an internal calculated value
The sampling logic follows the specified priority logic:
1. Filter out all the bets that have a processed_timestamp != 0 to get a list of new bets.
2. If the list of new bets is not empty:
2.1 Order the list in decreasing order of liquidity (highest liquidity first).
2.2 For bets with the same liquidity, order them in decreasing order of market closing time (openingTimestamp).
3. If the list of new bets is empty:
3.1 Order the bets in decreasing order of invested_amount.
3.2 For bets with the same invested_amount, order them in increasing order of processed_timestamp (least recently processed first).
3.3 For bets with the same invested_amount and processed_timestamp, order them in decreasing order of liquidity.
3.4 For bets with the same invested_amount, processed_timestamp, and liquidity, order them in decreasing order of market closing time (openingTimestamp).
Updates the investment amount and transaction timestamp if reedeem round is reached from post_tx_round
Co-authored-by: Anna Sambrook <[email protected]>
… into hotfix/staking-kpi-reachability
… exhausted." This reverts commit 8d3b9af.
The tx-submiter check for betplacement round assures that, PostTxSettlementRound was successful after bet placement round and transaction settlement skill was over with "DONE" event.
- Only three level of queues exist -1, 0, 1 - blacklisted bets are set to -1
- frameworks makes the setup call automatically. Co-Authored-By: Adamantios Zaras <[email protected]>
Co-Authored-By: Adamantios Zaras <[email protected]>
- anyother cicrcumstane of bet instance is not possible
Otherwise, the `tx_submitter` will not be available in the db for the current period, and either way it would not make sense to update the transaction information for a past period's decision.
Previously, we were only aware of a new epoch if our own agent was the one to call the checkpoint. If any other agent had called it, then we would never be aware of this event. Instead, we are now tracking changes to the ts checkpoint of the contract which only and always gets updated after a new epoch is triggered.
Hotfix/staking kpi reachability
Here is the license: https://github.com/python-attrs/attrs/blob/24.3.0/LICENSE However, the tool was reporting `UNKNOWN` license before authorizing it explicitly: gathering licenses... 132 packages and dependencies. check authorized packages... 131 packages. check unknown packages... 1 package. attrs (24.3.0): UNKNOWN dependencies: attrs << aiohttp << open-autonomy attrs << aiohttp << web3 << open-aea-ledger-ethereum << open-aea-test-autonomy attrs << hypothesis attrs << jsonschema << cosmpy << open-aea-ledger-cosmos attrs << jsonschema << open-aea << open-aea-cli-ipfs << open-autonomy attrs << jsonschema << open-aea << open-aea-ledger-cosmos attrs << jsonschema << open-aea << open-aea-ledger-ethereum attrs << jsonschema << open-aea << open-aea-test-autonomy attrs << jsonschema << open-aea << open-autonomy attrs << jsonschema << open-autonomy attrs << jsonschema << openapi-schema-validator << openapi-core attrs << jsonschema << openapi-schema-validator << openapi-spec-validator << openapi-core attrs << jsonschema << openapi-spec-validator attrs << jsonschema << valory-docker-compose << open-autonomy attrs << jsonschema << web3 attrs << pytest << open-aea-cli-ipfs attrs << pytest << open-aea-test-autonomy attrs << pytest << open-autonomy attrs << pytest << pytest-asyncio attrs << pytest << pytest-cov attrs << pytest << pytest-randomly attrs << pytest << pytest-rerunfailures
annasambrook
approved these changes
Dec 16, 2024
dagacha
approved these changes
Dec 16, 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.
No description provided.