vertex-ai-models: Wayback snapshot doesn't match the live feed

Abierto
#83 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go

Línea de trabajo

Start by locating the vertex-ai-models plugin and its kit.Cite check, then inspect how it reads the live feed and Wayback snapshot. Determine whether feed changes or stale captures cause the mismatch, and compare the options in the issue. Add a golden test for the chosen behavior; done means new deprecations are stored on consecutive daily runs while every stored event still has a matching citation.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

good first issue story

Story

As a team relying on Google Vertex AI model deprecations, we want vertex-ai-models to store its events even when the Wayback Machine's snapshot lags behind the live feed.

What happens

On 2026-11-18, vertex-ai-models refused to store anything: kit.Cite found that the Wayback snapshot didn't match the live feed. That's the citation check working as designed ("no provenance, no event"), but if the archive keeps serving a stale copy, the plugin reports nothing day after day.

Subtasks

  • Find out why: the feed changes often (each new release note changes the bytes), or the archive serves an older capture
  • Decide the fix: compare only the entries the plugin uses rather than the whole feed, retry the snapshot later, or cite the entry's own permalink
  • Golden test for the chosen behaviour

Acceptance criteria

  • Two daily runs in a row store Vertex AI deprecations when the feed has new ones
  • An event is still never stored without a matching citation
Lenguaje dominante
Go
Estrellas
0
Forks
0
Merge medio
2 h 59 min
PR fusionados (30 d)
17

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de patch-it-dev/patch-it-plugins

Todos los issues de patch-it-dev/patch-it-plugins

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.