Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

FB-011: fill-forward walk is O(tick_index) per lookup [minor, performance]

Open
#30 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python

Research direction

Start by reading context.py around lines 248 and 367, where get_spot and _get_bar_with_lag walk backward through ticks. Compare the per-instrument sorted-index and cached-pointer approaches described in the issue, then check for relevant tests in the repository. Done means missing-bar lookups avoid scanning every prior tick while returning the correct prior bar.

Written by the indexing model from the issue text.

Description

bug

Severity: minor (performance) · Source: BUGS_FASTBT.md (2026-10-09)

For an instrument with no bar at the current tick, _get_bar_with_lag and get_spot walk back tick by tick (context.py:367, :248). In a monthly period (~9,000 ticks), every lookup on a missing strike walks back across the whole period.

Fix: a per-instrument sorted index with bisect, or a cached last-seen pointer.

Dominant language
Python
Stars
28
Forks
17
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from uberdeveloper/fastbt

All issues in uberdeveloper/fastbt

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.