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

The fleet has produced no bundle since 2026-09-10: the daily Observe job is refused before it starts

Aperta
  • Qualcosa non va?
#32 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
1/5
Tempo stimato
Meno di un'ora
Idoneità per principianti
12/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github-actions, python
Ambito
devops, infrastructure

Direzione di ricerca

This requires an owner action in the account hosting the private history store, rather than a repository code change. Check that account’s Actions billing or spending limit, then manually trigger the store’s Observe workflow with workflow_dispatch and confirm the job starts. Done means scheduled runs resume and produce new bundles.

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

Descrizione

Found by the review of 2026-09-25 while checking the fleet's daily run in the history store.

What happens

The daily Observe workflow in the history store has not run its job since 2026-09-11. Every scheduled run from 2026-09-11 to 2026-09-25, fifteen in a row, ends in failure with an empty step list, and the job's single annotation says:

The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings

The last committed observation is observe: 2026-09-10T09:46:18Z. Nothing in this repository changed on 2026-09-11 (master has been a8726f5 = v0.1.8 since 2026-09-07), and the history store's workflow file has not changed since it moved its pin to v0.1.8. The cause is on the account hosting the private store: the job is refused by GitHub Actions before a runner is assigned, which is what a spending limit or a failed payment does for a private repository. The public repository is unaffected: CI, Released pins resolve and the weekly Self-observation all keep running, because public repositories do not consume paid minutes.

Why it matters

  • The fleet has fifteen days without a bundle. Every project's next bundle will compare against 2026-09-10; that is COMPARABLE (the store keeps the last verified bundle), but the activity.json interval will span the gap and carry INTERVAL_EXCEEDS_EVIDENCE_WINDOW for anything older than 28 days once the outage passes that length.
  • PV-CAL-004 (predictive validity of the attention order) counts calendar days of bundles. The evidence window it needs now has a hole from 2026-09-11 on; the calibration dataset the owner has to deliver cannot be taken from the store until the run is back.
  • The local store copy used for verification in this repository (devostasis-history, 308 bundles) is current up to 2026-09-10 only, for the same reason.

What is needed

This is an owner action, not a code change: check the account's Actions billing or spending limit, then trigger Observe manually (workflow_dispatch) to confirm the job starts, and let the schedule resume. Nothing in the engine or the store needs repair for this.

One unrelated notice from the same job annotations: ubuntu-latest migrates to Ubuntu 26 beginning 2026-10-19. The workflows here and in the store use ubuntu-latest with actions/setup-python, so nothing is expected to break, but the first run after that date is worth a look.

Lingua principale
Python
Stelle
4
Fork
1
Merge medio
2m
PR unite (30g)
2

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 drevendev/Devostasis

Tutte le issue di drevendev/Devostasis

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.