BuildCanada / BuildCanada/OutcomeTrackerAPI
Production activity feed has not updated since April 22, 2026
- 主要言語
- Ruby
- スター
- 5
- フォーク
- 10
- 平均マージ
- 5分
- マージ済み PR(30日)
- 3
説明
## Problem
The production API is reachable, but the activity feed appears stale. As of September 5, 2026, the newest record returned by:
```text
GET https://www.buildcanada.com/tracker/api/v1/feed.json?per_page=20
```
has `occurred_at: 2026-04-22T15:36:59Z`. The feed reports 11,121 total records, but none are newer than April 22.
The MCP backend is also operational through the existing wildcard proxy at:
```text
POST https://www.buildcanada.com/tracker/api/v1/mcp
```
I verified `initialize`, `tools/list`, and `tools/call` with `list_activity`; MCP returns the same April 22 records. This suggests the issue is in data ingestion/evaluation rather than the public API or MCP implementation itself.
## Expected
The configured `agent_weekly_scan` GoodJob cron runs every Sunday and creates current evaluation/activity records.
## Things to inspect
- GoodJob cron and worker history for `AgentWeeklyScanJob` and `AgentEvaluateCommitmentJob`
- failures from the Claude CLI subprocess, including OAuth/token errors
- worker connectivity to the Rails agent API
- production environment values for `RAILS_API_URL` and `AGENT_API_KEY`
One configuration worth checking: `AgentEvaluateCommitmentJob` defaults `RAILS_API_URL` to `http://localhost:3000`, while `docker-compose.prod.yml` runs GoodJob in a separate `worker` container and does not currently pass `RAILS_API_URL` into it. In that topology, localhost points to the worker container rather than the `web` service. This may not match the actual deployment and is therefore only a diagnostic lead, not a confirmed root cause.
The separate missing canonical MCP proxy route is being handled in BuildCanada/OutcomeTracker#169.
コントリビューションガイド
このリポジトリのコントリビューションガイドは索引されていません
調査の方向性
AgentWeeklyScanJob と AgentEvaluateCommitmentJob から始め、次に GoodJob の履歴と Claude CLI または worker のログを調べて失敗がないか確認します。docker-compose.prod.yml と RAILS_API_URL および AGENT_API_KEY の本番環境での値を確認し、worker が Rails API に到達できることを検証します。日曜日のスキャンによって 4 月 22 日より新しいアクティビティレコードが生成され、feed がそれらを返せば完了です。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- docker-compose, rails, ruby
- 領域
- api, backend, devops
- issue の種類
- バグ
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 活発さ
- 活発
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 52/100