Skip to content
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

Implement saving virtual orders into state #487

Merged
merged 20 commits into from
Aug 20, 2019

Commits on Feb 19, 2019

  1. Configuration menu
    Copy the full SHA
    14b0f5f View commit details
    Browse the repository at this point in the history

Commits on Mar 8, 2019

  1. Change saved virtual orders purge logic

    Purge saved virtual orders only if no buy AND sell orders. If we have
    both buy and sell real orders, restore both. If we have only one type of
    orders, restore corresponding virtual orders and purge opposite orders.
    bitphage committed Mar 8, 2019
    Configuration menu
    Copy the full SHA
    311c51a View commit details
    Browse the repository at this point in the history
  2. Prevent AttributeError when getting stored orders

    AttributeError: 'NoneType' object has no attribute 'values'
    bitphage committed Mar 8, 2019
    Configuration menu
    Copy the full SHA
    3db709a View commit details
    Browse the repository at this point in the history

Commits on Jul 29, 2019

  1. Configuration menu
    Copy the full SHA
    a94d1b9 View commit details
    Browse the repository at this point in the history

Commits on Aug 1, 2019

  1. Use uuid.uuid4 for VirtualOrder id

    This is more clean than using a price as id.
    bitphage committed Aug 1, 2019
    Configuration menu
    Copy the full SHA
    4cf38b0 View commit details
    Browse the repository at this point in the history
  2. Extend "orders" table

    Add new columns "virtual" and "custom" to Orders table. "Virtual" is for
    indicating virtual order, "Custom" is for adding any custom data in
    string format, may be used by any strategy to add additional info about
    order.
    
    This commit also introduces database migrations mechanism via alembic
    tool. Seems like it's the best solution for sqlalchemy to handle schema
    updates.
    bitphage committed Aug 1, 2019
    Configuration menu
    Copy the full SHA
    72a1cf6 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    49d255d View commit details
    Browse the repository at this point in the history
  4. Refactor SO virtual orders save/restore

    Use new storage methods to save/restore virtual orders
    bitphage committed Aug 1, 2019
    Configuration menu
    Copy the full SHA
    3288e54 View commit details
    Browse the repository at this point in the history
  5. Overriding sqlite db file isn't working

    Add notice, add workaround to purge test worker orders from the db on
    teradown.
    bitphage committed Aug 1, 2019
    Configuration menu
    Copy the full SHA
    2c89eb2 View commit details
    Browse the repository at this point in the history
  6. Reformat with black

    bitphage committed Aug 1, 2019
    Configuration menu
    Copy the full SHA
    dd4c7ea View commit details
    Browse the repository at this point in the history
  7. Configuration menu
    Copy the full SHA
    4aae075 View commit details
    Browse the repository at this point in the history

Commits on Aug 7, 2019

  1. Configuration menu
    Copy the full SHA
    aec108a View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    27c513c View commit details
    Browse the repository at this point in the history
  3. Implement clear_orders_extended()

    New method is needed to be able selectively remove orders from the db.
    bitphage committed Aug 7, 2019
    Configuration menu
    Copy the full SHA
    7af08b4 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    09cf799 View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    70c3745 View commit details
    Browse the repository at this point in the history
  6. Configuration menu
    Copy the full SHA
    e56f966 View commit details
    Browse the repository at this point in the history
  7. Refactor operational depth handling

    * Operational depth following is strict now (don't keep additional 5
      orders on price movements)
    * Order size check is removed as orders are kept in state and not
      restored from scratch
    * Order replacement is now happening in single `for` cycle instead of
      one-per-maintenance
    bitphage committed Aug 7, 2019
    Configuration menu
    Copy the full SHA
    2e35dfe View commit details
    Browse the repository at this point in the history
  8. Configuration menu
    Copy the full SHA
    1a320a5 View commit details
    Browse the repository at this point in the history

Commits on Aug 8, 2019

  1. Configuration menu
    Copy the full SHA
    b73d2af View commit details
    Browse the repository at this point in the history