Give every review round a share of the replan collector's comment budget

Aperta
  • Qualcosa non va?
#457 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
Mezza giornata
Idoneità per principianti
66/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
python
Ambito
tooling

Direzione di ricerca

Start with HistoricalReviewCollector.collect in replan.py, around lines 174-202, where the single 24,000-character budget is filled in round order. Change it so each round with findings gets a share of the budget and the newest rounds are filled first, with clipped bodies marked and linked to their comment URL. Done when twelve rounds of 4 KB comments yield twelve represented rounds within the same total bound, a short history renders in full, and the fence-escaping is unchanged; check this with the existing collector tests.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement

Problem

HistoricalReviewCollector.collect gives the replacement agent review comment bodies from a single 24,000-character budget, filled in round order (replan.py:174-202). On a long PR, the newest rounds, which usually show best why the PR is being replaced, are the ones dropped.

Evidence

In #451, the REPLAN_REEXECUTE prompt for Lychee-Technology/forma#801 contained comment bodies for rounds 1–7 only, with round 7 cut mid-sentence. Rounds 8–12 were absent. The impact there was small, because every round's findings were rendered separately (13.4 KB) and the agent still diagnosed the root cause.

Desired outcome

Every round that ended with findings gets a share of the budget, for example max(1500, budget // rounds), filled newest first. Each clipped body says it was clipped and where the full text is (the comment URL). The total bound is unchanged.

Acceptance criteria

  • Twelve rounds of 4 KB comments yield twelve represented rounds within 24,000 characters, each clipped body marked.
  • A short history is rendered in full, as today.
  • The fence-escaping of collected text is unchanged.

Trade-offs and unknowns

Per-round clipping may cut every body short instead of showing a few in full. The findings remain complete either way, and the comment URLs let the agent read any body in full.

Lingua principale
Python
Stelle
0
Fork
0
Merge medio
5h 42m
PR unite (30g)
110

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di iceboundrock/AutoForge

Tutte le issue di iceboundrock/AutoForge

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.