Skip to content

chore: remove option-chain snapshotter remnants - #267

Merged
moremeds merged 2 commits into
masterfrom
chore/remove-option-chain-snapshotter
Nov 2, 2026
Merged

moremeds merged 2 commits into
masterfrom
chore/remove-option-chain-snapshotter

Conversation

@moremeds

@moremeds moremeds commented Nov 2, 2026

Copy link
Copy Markdown
Owner

Summary

The option-chain snapshotter daemon never shipped (PR #165 closed unmerged). Remove what it left on master:

  • CLIENT_IDS["option_chain_snapshotter_a" / "_b"] (95 / 96) in src/xenon/clients/ib_client.py
  • LOCK_KEY_OPTION_CHAIN_SNAPSHOTTER in src/xenon/api/services/advisory_lock.py
  • scripts/tests/test_option_chain_snapshotter_registry.py (only pinned those values)

Not touched: /health snapshotter and the Operator console "Snapshotter" tile — that is account-snapshot freshness, not the option-chain daemon.

Test plan

  • git grep option_chain_snapshotter|LOCK_KEY_OPTION_CHAIN in src/scripts/web: no references left
  • ruff check --select F src scripts: clean
  • CI python-tests (local PG test DB schema is behind; CI is the gate)

chenxi added 2 commits November 2, 2026 17:32
The snapshotter daemon never shipped (PR #165 closed unmerged). Drop
its reserved clientIds 95/96, its advisory-lock key and the registry
test that pinned them. /health "snapshotter" (account-snapshot
freshness) is unrelated and stays.
@moremeds
moremeds merged commit e673ad9 into master Nov 2, 2026
8 checks passed
@moremeds
moremeds deleted the chore/remove-option-chain-snapshotter branch November 2, 2026 09:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant