-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release/v1.2.0 (Mar 2022 release) #5206
Merged
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
…d deserialization
…ad of the db_timestamp. The creation_timestamp has been added to order creation event. Including creation_timestamp in HangingOrder. The logic to calculate order age has been updated
…e after storing it in the DB
…anage timestamps in seconds (as the connectors and strategies). Update in order creation event and order fill event to manage timestamps in seconds. Change in market recorder to handle timestamps from events as seconds
…d deserialization
…ad of the db_timestamp. The creation_timestamp has been added to order creation event. Including creation_timestamp in HangingOrder. The logic to calculate order age has been updated
…e after storing it in the DB
…anage timestamps in seconds (as the connectors and strategies). Update in order creation event and order fill event to manage timestamps in seconds. Change in market recorder to handle timestamps from events as seconds
- Adds global config map restoring after interface util tests.
…ing' into feature/improving_tables_formatting
…d deserialization
…ad of the db_timestamp. The creation_timestamp has been added to order creation event. Including creation_timestamp in HangingOrder. The logic to calculate order age has been updated
…e after storing it in the DB
…anage timestamps in seconds (as the connectors and strategies). Update in order creation event and order fill event to manage timestamps in seconds. Change in market recorder to handle timestamps from events as seconds
…ps://github.com/CoinAlpha/hummingbot into feat/add_creation_timestamp_to_in_flight_orders after rebasing with development
…_fill_in_order_tracker
…om_order_fill_in_order_tracker Feat/separate order update from order fill in order tracker
…on_1.2.0 fix / development version from dev-1.0.0 to dev-1.2.0
Feat/ PMM - Split and allow multiple order level spread
feat / change version 1.2.0
…_branches_staging
…_in_all_branches_staging Changes reapplied on top of staging branch
refactor/ update connector status in the client for v1.2.0
feat/merge-staging
… feat/solve_merge_problems_staging_and_master
…ging_and_master feat/solve merge problems staging and master
rapcmia
approved these changes
Mar 31, 2022
phbrgnomo
approved these changes
Mar 31, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
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.
Before submitting this PR, please make sure:
A description of the changes proposed in the pull request:
February 2022
staging
candidate for March releaseTests performed by the developer:
Tips for QA testing: