Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

cloud-lab: combined pytest run red on main — cumulative in-memory sessions break fee/allotment assertions; clientd offer-string drift

Aperta
  • Qualcosa non va?
#792 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
1-2 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
testing-qa

Direzione di ricerca

Start with the offer-string mismatch: test_list_offers_parses_real_advertisement expects 1 sats/step, while scripts/tollgate-clientd.py prints 1 sat/step, so align one side and confirm that test passes alone. The cumulative-allotment failures come from in-memory sessions on the static MAC 02:00:00:00:00:20 shared across files; test_external_mints.py has a _mac() helper that shows the per-file MAC approach. Done means the combined pytest run is green, but the isolation strategy (randomized MACs, a session-reset fixture, or a documented segmented run) still needs a maintainer decision.

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

Descrizione

The standard combined suite invocation on main (cb4db7f, verified 2026-10-09 on the ai-legion lab host; identical shape on PR #771 head b3ce6d5) fails 6 tests:

  • test_fee_is_sum_then_ceil[255/1023/2047], test_above_swap_fee_succeeds_with_fee_deducted, test_fee_mint_payments_do_not_break_the_free_mint_path: the session event's allotment is cumulative per client MAC (in-memory sessions — the cloud-lab README already notes "sessions are in-memory per client MAC"), so per-payment assertions break once earlier payments or the clientd renewal daemon (test_clientd_autotopup.py runs earlier alphabetically in the same invocation) have accumulated time on the static client MAC 02:00:00:00:00:20. Attribution verified empirically: [255] passes on a freshly restarted upstream, and a main-built upstream fails identically to the PR head — pre-existing on main, not a #771 regression.
  • test_list_offers_parses_real_advertisement: expects 1 sats/step, scripts/tollgate-clientd.py prints 1 sat/step.

Impact: the combined client pytest -sv invocation cannot serve as a green gate — the next lane that runs it as-is will re-triage the same six failures.

Suggested directions: per-file randomized client MACs (precedent: _mac() in test_external_mints.py), a session-reset fixture between files, or documenting a canonical segmented invocation; align the clientd string expectation.

Evidence (lane host, session rc1-771): /root/src/rel-771-logs/std-suite-pytest.log, attribution runs described in /root/src/rel-771-transcript.md §4.5, summary in /root/src/rel-771-handoff.md Appendix B.

Lingua principale
Go
Stelle
12
Fork
14
Merge medio
1g 7h
PR unite (30g)
205

Preparare l'ambiente

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 OpenTollGate/tollgate-module-basic-go

Tutte le issue di OpenTollGate/tollgate-module-basic-go

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.