fix(algo): /api/algo/execute takes an unbounded window
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Read dashboard/backend/domain/backtesting/algo_service.py around execute_algo and compare its POST /api/algo/execute path with the 14-day cap and copy described for POST /backtest/run. Then inspect app.html near line 1462 and app.js near line 12273 to trace the Trading Algo panel. Done means the cap decision and user-facing copy consistently describe the bounds for each surface.
Written by the indexing model from the issue text.
Description
Follow-up from #474 item 1 (PR #477).
PR #477 capped POST /backtest/run at MAX_BACKTEST_DAYS = 14 and shipped user-facing copy saying so. execute_algo (dashboard/backend/domain/backtesting/algo_service.py:353-420), behind POST /api/algo/execute, takes start_date/end_date and validates neither — no span check, no trading-day bound, no pipeline call estimate. It runs a real Alpaca + LLM backtest on a daemon thread inside the web process.
So the Trading Algo panel (app.html:1462 → app.js:12273) will still accept a six-month window that the Backtest panel now refuses, and there is no timeout backstop on that path either — it is a thread, not a subprocess.
Two things to decide, not one:
- Whether the 14-day cap should apply here at all (this surface is not the onboarding path the cap was calibrated for).
- If not, whether the shipped "up to 14 days" copy needs to say which surface it governs.
Either answer is fine; the current state — two surfaces into the same engine with opposite bounds and copy that names only one — is not.
- Dominant language
- Python
- Stars
- 767
- Forks
- 156
- Avg merge
- 22h 2m
- Merged PRs (30d)
- 88
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Open-Finance-Lab/AgenticTrading
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Open-Finance-Lab/AgenticTrading#663 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Open-Finance-Lab/AgenticTrading#661 ·
Maintainers usually reply within 1 day
-
fix(llm): a non-ASCII execution handoff raises UnicodeEncodeError instead of ExecutionHandoffErrorPossibly taken @subidhkhanal claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Open-Finance-Lab/AgenticTrading#659 ·
Maintainers usually reply within 1 day
-
fix(backtests): an LLM action with trailing whitespace ("buy ") is silently droppedPossibly taken @subidhkhanal claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Open-Finance-Lab/AgenticTrading#658 ·
Maintainers usually reply within 1 day
-
fix(llm): Gemini adapter drops thinking tokens from the output countPossibly taken @subidhkhanal claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Open-Finance-Lab/AgenticTrading#657 ·
Maintainers usually reply within 1 day
All issues in Open-Finance-Lab/AgenticTrading
Similar issues
-
good first issue infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
kuznia-rdzeni/coreblocks#1135 ·
-
good first issue server
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
documentation priority: high
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
a-lex-s/mealie-telegram-bot#54 ·
Maintainers usually reply within 1 day
-
type/test
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
SaltedTan/virgil-language-server#218 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
btclib-org/btclib-wallet#541 ·
Maintainers usually reply within 1 day