Skip to content

Document the stream request.security known issue (v1.0.0, v1.0.1) - #323

Merged
luisleo526 merged 1 commit into
mainfrom
lv/known-issue-stream-security
Oct 3, 2026
Merged

luisleo526 merged 1 commit into
mainfrom
lv/known-issue-stream-security

Conversation

@luisleo526

Copy link
Copy Markdown
Collaborator

Summary

Documents a known issue in the native stream of v1.0.0 and v1.0.1. When a stream's input timeframe equals its script timeframe, a strategy that requests its own chart symbol with request.security stops receiving new requested values after the first realtime bar. That includes ticker.heikinashi of the chart symbol and requests at timeframe.period. Its live results can then differ from a backtest of the same bars. Batch backtests are not affected.

  • docs/pages/streaming.md gains a Known issues section with the workaround: use a script timeframe larger than the input timeframe, or the batch backtest.
  • The README's native runner section points to it.

A fix to the stream is in progress as a separate change.

Documentation only: no source, test or behaviour change.

🤖 Generated with Claude Code

In a stream whose input timeframe equals its script timeframe, same-chart
request.security values stop updating after the first realtime bar. Batch
backtests are unaffected. The streaming page gains a Known issues section with
the workaround, and the README's native runner section points to it.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@luisleo526
luisleo526 merged commit 015dd9a into main Oct 3, 2026
13 checks passed
@luisleo526
luisleo526 deleted the lv/known-issue-stream-security branch October 3, 2026 23:12
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