fix(live): a catching-up entry renders as pending on the board
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript, python
- Domain
- frontend
Research direction
Start in js/live-leaderboard.js by reading liveEntryIsPending and the detail-panel code around line 312; the issue says the server already sends snapshot_end and live_status.catching_up. Update the display so catching-up entries show value and return, keep rank as "—", and include the catching-up label through snapshot_end. Bump the js/live-leaderboard.js?v=2 reference in app.html; done when the board and detail panel show the specified state.
Written by the indexing model from the issue text.
Description
#582 added status: "catching_up" for an entry more than one session behind the board's newest row: unranked, but it keeps its curve, value and return (_entry_from_strategy, domain/leaderboard/live.py:1227).
The frontend keys "pending" on rank == null (liveEntryIsPending, js/live-leaderboard.js:110), so a catching-up row shows rank, value and return as "—" and its detail panel says "Awaiting freeze" (:312), while the chart draws its line. The per-entry snapshot_end and live_status.catching_up the server sends for this are read nowhere.
Fix: treat status === 'catching_up' as printed but unranked — show value/return, rank "—", and a "Catching up · through snapshot_end" label. Bump js/live-leaderboard.js?v=2 in app.html.
- 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