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

FB-004: max_cycles counts per period, docstring says per day [trap]

Open
#23 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
45/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
backend

Research direction

Start with the engine docstring at engine.py:85 and the daily reset in strategy.py:416 to confirm how cycle counts work across periods. Then trace where max_cycles is enforced and how strategies set it; the issue notes 76 hard-coded uses across 67 files. Done means the docs describe the per-period behavior and an optional per-day budget is added.

Written by the indexing model from the issue text.

Description

bug

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

The engine docstring (engine.py:85) says "per day". current_cycle is reset only in _reset_for_new_day (strategy.py:416), which runs once per period. So max_cycles=1 means one trade per week or month, and a max_cycles == 1 guard in a strategy means something different in each mode.

Note: this repo's strategies carry 76 hard-coded max_cycles=1 across 67 files, turning re-entry strategies into single-entry ones.

Workaround: set max_cycles per period explicitly and enforce any per-day budget in strategy code.
Fix: document it as per-period, and add an optional per-day cycle budget.

Dominant language
Python
Stars
28
Forks
17
Avg merge
8h 50m
Merged PRs (30d)
2

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.