binance: set `Pair.pegInstructionsAllowed = False`

Lol, a cheeky unforeseen bug due to TOML's lack of a null type and thinking i can render an `Optional` field on a `msgspec.Struct` (defaulted to `None`) the `binance.symcache.toml` cache file.. I didn't catch this when i first updated to the 3.1 API in f7caa75228 because i never did a cache-files flush.. lesson learned and we **really need tests for this**!!
Wow, update root `conf.toml` to new multiaddr style
2025-10-02 20:08:56 -04:00 · 2025-10-02 20:07:23 -04:00
2 changed files with 6 additions and 4 deletions
--- a/config/conf.toml
+++ b/config/conf.toml
@ -1,7 +1,9 @@
 [network]
-tsdb.backend = 'marketstore'
-tsdb.host = 'localhost'
-tsdb.grpc_port = 5995
+pikerd = [
+  '/ipv4/127.0.0.1/tcp/6116',  # std localhost daemon-actor tree
+  # '/uds/6116',  # TODO std uds socket file
+]
+

 [ui]
 # set custom font + size which will scale entire UI
--- a/piker/brokers/binance/venues.py
+++ b/piker/brokers/binance/venues.py
@ -102,7 +102,7 @@ class Pair(Struct, frozen=True, kw_only=True):
    # https://developers.binance.com/docs/binance-spot-api-docs#2025-08-26
    # will become non-optional 2025-08-28?
    # https://developers.binance.com/docs/binance-spot-api-docs#future-changes
-    pegInstructionsAllowed: bool|None = None
+    pegInstructionsAllowed: bool = False

    filters: dict[
        str,