Release 1.190.0

See release notes.

.pre-commit-config.yaml

@@ -73,7 +73,7 @@ repos:
         types: [python]
 
   - repo: https://github.com/psf/black
-    rev: 24.2.0
+    rev: 24.3.0
     hooks:
       - id: black
         types_or: [python, pyi]
@@ -82,7 +82,7 @@ repos:
         exclude: "docs/_pygments/monokai.py"
 
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.3.2
+    rev: v0.3.4
     hooks:
       - id: ruff
         args: ["--fix"]

README.md

@@ -15,10 +15,10 @@
 
 | Platform           | Rust    | Python |
 | :----------------- | :------ | :----- |
-| `Linux (x86_64)`   | 1.76.0+ | 3.10+  |
-| `macOS (x86_64)`   | 1.76.0+ | 3.10+  |
-| `macOS (arm64)`    | 1.76.0+ | 3.10+  |
-| `Windows (x86_64)` | 1.76.0+ | 3.10+  |
+| `Linux (x86_64)`   | 1.77.0+ | 3.10+  |
+| `macOS (x86_64)`   | 1.77.0+ | 3.10+  |
+| `macOS (arm64)`    | 1.77.0+ | 3.10+  |
+| `Windows (x86_64)` | 1.77.0+ | 3.10+  |
 
 - **Website:** https://nautilustrader.io
 - **Docs:** https://docs.nautilustrader.io
@@ -135,20 +135,28 @@ This project makes the [Soundness Pledge](https://raphlinus.github.io/rust/2020/
 
 ## Integrations
 
-NautilusTrader is designed in a modular way to work with 'adapters' which provide
-connectivity to data providers and/or trading venues - converting their raw API
+NautilusTrader is designed in a modular way to work with _adapters_ which provide
+connectivity to trading venues and data providers - converting their raw API
 into a unified interface. The following integrations are currently supported:
 
 | Name                                                      | ID                    | Type                    | Status                                                  | Docs                                                                |
 | :-------------------------------------------------------- | :-------------------- | :---------------------- | :------------------------------------------------------ | :------------------------------------------------------------------ |
-| [Betfair](https://betfair.com)                            | `BETFAIR`             | Sports betting exchange | ![status](https://img.shields.io/badge/beta-yellow)     | [Guide](https://docs.nautilustrader.io/integrations/betfair.html)   |
-| [Binance](https://binance.com)                            | `BINANCE`             | Crypto exchange (CEX)   | ![status](https://img.shields.io/badge/stable-green)    | [Guide](https://docs.nautilustrader.io/integrations/binance.html)   |
-| [Binance US](https://binance.us)                          | `BINANCE`             | Crypto exchange (CEX)   | ![status](https://img.shields.io/badge/stable-green)    | [Guide](https://docs.nautilustrader.io/integrations/binance.html)   |
-| [Binance Futures](https://www.binance.com/en/futures)     | `BINANCE`             | Crypto exchange (CEX)   | ![status](https://img.shields.io/badge/stable-green)    | [Guide](https://docs.nautilustrader.io/integrations/binance.html)   |
-| [Bybit](https://www.bybit.com)                            | `BYBIT`               | Crypto exchange (CEX)   | ![status](https://img.shields.io/badge/building-orange) |                                                                     |
-| [Databento](https://databento.com)                        | `DATABENTO`           | Data provider           | ![status](https://img.shields.io/badge/beta-yellow)     | [Guide](https://docs.nautilustrader.io/integrations/databento.html) |
+| [Betfair](https://betfair.com)                            | `BETFAIR`             | Sports Betting Exchange | ![status](https://img.shields.io/badge/stable-green)    | [Guide](https://docs.nautilustrader.io/integrations/betfair.html)   |
+| [Binance](https://binance.com)                            | `BINANCE`             | Crypto Exchange (CEX)   | ![status](https://img.shields.io/badge/stable-green)    | [Guide](https://docs.nautilustrader.io/integrations/binance.html)   |
+| [Binance US](https://binance.us)                          | `BINANCE`             | Crypto Exchange (CEX)   | ![status](https://img.shields.io/badge/stable-green)    | [Guide](https://docs.nautilustrader.io/integrations/binance.html)   |
+| [Binance Futures](https://www.binance.com/en/futures)     | `BINANCE`             | Crypto Exchange (CEX)   | ![status](https://img.shields.io/badge/stable-green)    | [Guide](https://docs.nautilustrader.io/integrations/binance.html)   |
+| [Bybit](https://www.bybit.com)                            | `BYBIT`               | Crypto Exchange (CEX)   | ![status](https://img.shields.io/badge/building-orange) |                                                                     |
+| [Databento](https://databento.com)                        | `DATABENTO`           | Data Provider           | ![status](https://img.shields.io/badge/beta-yellow)     | [Guide](https://docs.nautilustrader.io/integrations/databento.html) |
 | [Interactive Brokers](https://www.interactivebrokers.com) | `INTERACTIVE_BROKERS` | Brokerage (multi-venue) | ![status](https://img.shields.io/badge/stable-green)    | [Guide](https://docs.nautilustrader.io/integrations/ib.html)        |
 
+- `ID:` The default client ID for the integrations adapter clients
+- `Type:` The type of integration (often the venue type)
+
+### Status
+- `building` - Under construction and likely not in a usable state
+- `beta` - Completed to a minimally working state and in a 'beta' testing phase
+- `stable` - Stabilized feature set and API, the integration has been tested by both developers and users to a reasonable level (some bugs may still remain)
+
 Refer to the [Integrations](https://docs.nautilustrader.io/integrations/index.html) documentation for further details.
 
 ## Installation

RELEASES.md

@@ -1,11 +1,38 @@
+# NautilusTrader 1.190.0 Beta
+
+Released on 22nd March 2024 (UTC).
+
+### Enhancements
+- Added Databento adapter `continuous`, `parent` and `instrument_id` symbology support (will infer from symbols)
+- Added `DatabaseConfig.timeout` config option for timeout seconds to wait for a new connection
+- Added CSV tick and bar data loader params, thanks @rterbush
+- Implemented `LogGuard` to ensure global logger is flushed on termination, thanks @ayush-sb and @twitu
+- Improved Interactive Brokers client connectivity resilience and component lifecycle, thanks @benjaminsingleton
+- Improved Binance execution client ping listen key error handling and logging
+- Improved Redis cache adapter and message bus error handling and logging
+- Improved Redis port parsing (`DatabaseConfig.port` can now be either a string or integer)
+- Refactored `InteractiveBrokersEWrapper`, thanks @rsmb7z
+- Redact Redis passwords in strings and logs
+- Upgraded `redis` crate to 0.25.2 which bumps up TLS dependencies, and turned on `tls-rustls-webpki-roots` feature flag
+
+### Breaking Changes
+None
+
+### Fixes
+- Fixed JSON format for log file output (was missing `timestamp` and `trader\_id`)
+- Fixed `DatabaseConfig` port JSON parsing for Redis (was always defaulting to 6379)
+- Fixed `ChandeMomentumOscillator` indicator divide by zero error (both Rust and Cython versions)
+
+---
+
 # NautilusTrader 1.189.0 Beta
 
 Released on 15th March 2024 (UTC).
 
 ### Enhancements
 - Implemented Binance order book snapshot rebuilds on websocket reconnect (see integration guide)
 - Added additional validations for `OrderMatchingEngine` (will now raise a `RuntimeError` when a price or size precision for `OrderFilled` does not match the instruments precisions)
-- Added `LoggingConfig.use_pyo3` option for pyo3 based logging initialization (worse performance but allows visibility into logs originating from Rust)
+- Added `LoggingConfig.use_pyo3` config option for pyo3 based logging initialization (worse performance but allows visibility into logs originating from Rust)
 - Added `exchange` field to `FuturesContract`, `FuturesSpread`, `OptionsContract` and `OptionsSpread` (optional)
 
 ### Breaking Changes

docs/concepts/data.md

@@ -41,7 +41,7 @@ To achieve this, two main components are necessary:
 ### Data loaders
 
 Data loader components are typically specific for the raw source/format and per integration. For instance, Binance order book data is stored in its raw CSV file form with
-an entirely different format to [Databento Binary Encoding (DBN)](https://docs.databento.com/knowledge-base/new-users/dbn-encoding/getting-started-with-dbn) files.
+an entirely different format to [Databento Binary Encoding (DBN)](https://databento.com/docs/knowledge-base/new-users/dbn-encoding/getting-started-with-dbn) files.
 
 ### Data wranglers
 

docs/integrations/databento.md

@@ -1,10 +1,10 @@
 # Databento
 
 ```{warning}
-We are currently working on this integration guide - consider it incomplete for now.
+We are currently working on this integration guide.
 ```
 
-NautilusTrader provides an adapter for integrating with the Databento API and [Databento Binary Encoding (DBN)](https://docs.databento.com/knowledge-base/new-users/dbn-encoding) format data.
+NautilusTrader provides an adapter for integrating with the Databento API and [Databento Binary Encoding (DBN)](https://databento.com/docs/knowledge-base/new-users/dbn-encoding) format data.
 As Databento is purely a market data provider, there is no execution client provided - although a sandbox environment with simulated execution could still be set up.
 It's also possible to match Databento data with Interactive Brokers execution, or to calculate traditional asset class signals for crypto trading.
 
@@ -17,7 +17,7 @@ The capabilities of this adapter include:
 [Databento](https://databento.com/signup) currently offers 125 USD in free data credits (historical data only) for new account sign-ups.
 
 With careful requests, this is more than enough for testing and evaluation purposes.
-It's recommended you make use of the [/metadata.get_cost](https://docs.databento.com/api-reference-historical/metadata/metadata-get-cost) endpoint.
+It's recommended you make use of the [/metadata.get_cost](https://databento.com/docs/api-reference-historical/metadata/metadata-get-cost) endpoint.
 ```
 
 ## Overview
@@ -44,13 +44,13 @@ and won't need to necessarily work with these lower level components directly.
 
 ## Databento documentation
 
-Databento provides extensive documentation for users which can be found in the [Databento knowledge base](https://docs.databento.com/knowledge-base/new-users).
-It's recommended you also refer to the Databento documentation in conjunction with this Nautilus integration guide.
+Databento provides extensive documentation for users which can be found in the [Databento knowledge base](https://databento.com/docs/knowledge-base/new-users).
+It's recommended you also refer to this Databento documentation in conjunction with this NautilusTrader integration guide.
 
 ## Databento Binary Encoding (DBN)
 
 Databento Binary Encoding (DBN) is an extremely fast message encoding and storage format for normalized market data.
-The [DBN specification](https://docs.databento.com/knowledge-base/new-users/dbn-encoding) includes a simple, self-describing metadata header and a fixed set of struct definitions,
+The [DBN specification](https://databento.com/docs/knowledge-base/new-users/dbn-encoding) includes a simple, self-describing metadata header and a fixed set of struct definitions,
 which enforce a standardized way to normalize market data.
 
 The integration provides a decoder which can convert DBN format data to Nautilus objects.
@@ -91,7 +91,7 @@ The Nautilus decoder will use the Databento `raw_symbol` for the Nautilus `symbo
 from the Databento instrument definition message for the Nautilus `venue`.
 
 Databento datasets are identified with a *dataset code* which is not the same
-as a venue identifier. You can read more about Databento dataset naming conventions [here](https://docs.databento.com/api-reference-historical/basics/datasets).
+as a venue identifier. You can read more about Databento dataset naming conventions [here](https://databento.com/docs/api-reference-historical/basics/datasets).
 
 Of particular note is for CME Globex MDP 3.0 data (`GLBX.MDP3` dataset code), the following
 exchanges are all grouped under the `GLBX` venue. These mappings can be determined from the
@@ -105,7 +105,7 @@ instruments `exchange` field:
 - `XNYM` - **New York Mercantile Exchange (NYMEX)**
 
 ```{note}
-Other venue MICs can be found in the `venue` field of responses from the [metadata.list_publishers](https://docs.databento.com/api-reference-historical/metadata/metadata-list-publishers?historical=http&live=python) endpoint.
+Other venue MICs can be found in the `venue` field of responses from the [metadata.list_publishers](https://databento.com/docs/api-reference-historical/metadata/metadata-list-publishers?historical=http&live=python) endpoint.
 ```
 
 ## Timestamps
@@ -127,33 +127,37 @@ When decoding and normalizing Databento to Nautilus we generally assign the Data
 
 ```{note}
 See the following Databento docs for further information:
-- [Databento standards and conventions - timestamps](https://docs.databento.com/knowledge-base/new-users/standards-conventions/timestamps)
-- [Databento timestamping guide](https://docs.databento.com/knowledge-base/data-integrity/timestamping/timestamps-on-databento-and-how-to-use-them)
+- [Databento standards and conventions - timestamps](https://databento.com/docs/knowledge-base/new-users/standards-conventions/timestamps)
+- [Databento timestamping guide](https://databento.com/docs/knowledge-base/data-integrity/timestamping/timestamps-on-databento-and-how-to-use-them)
 ```
 
 ## Data types
 
 The following section discusses Databento schema -> Nautilus data type equivalence
 and considerations.
 
+```{note}
+See the Databento [list of fields by schema guide](https://databento.com/docs/knowledge-base/new-users/fields-by-schema).
+```
+
 ### Instrument definitions
 
 Databento provides a single schema to cover all instrument classes, these are
 decoded to the appropriate Nautilus `Instrument` types.
 
 The following Databento instrument classes are supported by NautilusTrader:
 
-| Databento instrument class | Nautilus instrument type     |
-|----------------------------|------------------------------|
-| STOCK                      | `Equity`                     |
-| FUTURE                     | `FuturesContract`            |
-| CALL                       | `OptionsContract`            |
-| PUT                        | `OptionsContract`            |
-| FUTURESPREAD               | `FuturesSpread`              |
-| OPTIONSPREAD               | `OptionsSpread`              |
-| MIXEDSPREAD                | `OptionsSpread`              |
-| FXSPOT                     | `CurrencyPair`               |
-| BOND                       | Not yet available            |
+| Databento instrument class | Code |  Nautilus instrument type    |
+|----------------------------|------|------------------------------|
+| Stock                      | `K`  | `Equity`                     |
+| Future                     | `F`  | `FuturesContract`            |
+| Call                       | `C`  | `OptionsContract`            |
+| Put                        | `P`  | `OptionsContract`            |
+| Future spread              | `S`  | `FuturesSpread`              |
+| Option spread              | `T`  | `OptionsSpread`              |
+| Mixed spread               | `M`  | `OptionsSpread`              |
+| FX spot                    | `X`  | `CurrencyPair`               |
+| Bond                       | `B`  | Not yet available            |
 
 ### MBO (market by order)
 
@@ -171,9 +175,9 @@ object, which occurs during the replay startup sequence.
 
 ### MBP-1 (market by price, top-of-book)
 
-This schema represents the top-of-book only. Like with MBO messages, some
+This schema represents the top-of-book only (quotes *and* trades). Like with MBO messages, some
 messages carry trade information, and so when decoding MBP-1 messages Nautilus 
-will produce a `QuoteTick` and also a `TradeTick` if the message is a trade.
+will produce a `QuoteTick` and *also* a `TradeTick` if the message is a trade.
 
 ### OHLCV (bar aggregates)
 
@@ -183,9 +187,9 @@ The Nautilus decoder will normalize the `ts_event` timestamps to the **close** o
 
 ### Imbalance & Statistics
 
-The Databento `imbalance` and `statistics` schemas cannot be represented as a built-in Nautilus data types
+The Databento `imbalance` and `statistics` schemas cannot be represented as a built-in Nautilus data types,
 and so they have specific types defined in Rust `DatabentoImbalance` and `DatabentoStatistics`.
-Python bindings are provided via pyo3 (Rust) and so the types behaves a little differently to a built-in Nautilus
+Python bindings are provided via pyo3 (Rust) so the types behave a little differently to a built-in Nautilus
 data types, where all attributes are pyo3 provided objects and not directly compatible
 with certain methods which may expect a Cython provided type. There are pyo3 -> legacy Cython
 object conversion methods available, which can be found in the API reference.
@@ -244,7 +248,7 @@ the Nautilus Parquet data from disk, which achieves extremely high through-put (
 than converting DBN -> Nautilus on the fly for every backtest run).
 
 ```{note}
-Performance benchmarks are under development.
+Performance benchmarks are currently under development.
 ```
 
 ## Loading DBN data