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

admin: drop unread platform_model_cost_micro_usd

Open Beginner friendly
#591 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
67/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
python

Research direction

Start by checking the /api/admin/analytics/commercial and /api/admin/analytics/operational response definitions and the named fixtures and test_value_queries.py assertions. Confirm whether an external consumer of these routes is known before removing the field. Done means the field is removed from both responses and those fixtures and assertions are updated, with the relevant tests passing.

Written by the indexing model from the issue text.

Description

Since #589 the Credits & Cost detail page reads platform cost from /overview (platform_model_cost_usd), the same number as the tile. Nothing in dashboard/frontend/ reads platform_model_cost_micro_usd any more.

It is still computed and returned by:

  • /api/admin/analytics/commercial: CommercialAnalyticsResponse, via legacy_service.get_platform_model_cost_micro (cheap since #589, but a second copy of the overview figure).
  • /api/admin/analytics/operational: OperationalAnalyticsResponse.

Proposal: drop it from both responses, plus the fixtures (tests/fixtures/admin_analytics/{commercial,operational}.json, target/operational.json) and the test_value_queries.py assertions. Keep it if an external consumer of these routes is known.

Found during the #589 review.

Dominant language
Python
Stars
767
Forks
156
Avg merge
22h 57m
Merged PRs (30d)
84

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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 Open-Finance-Lab/AgenticTrading

All issues in Open-Finance-Lab/AgenticTrading

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.