No description
4f5c71e811
All checks were successful
Build & Push Container Image / build (push) Successful in 10s
Saving an estimate of 0 caused advanceToNext to re-poker the same issue repeatedly: !0 is true and 0 === 0 matches the "unestimated" check. Track pokered issues with an `estimated` flag so they are skipped regardless of estimate value. Also guard against empty session index entries in createScopedSession (NATS KV tombstones after delete can return empty values, producing an invalid trailing-dot key that crashes Bucket.get). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .forgejo/workflows | ||
| backend | ||
| frontend | ||
| grafana | ||
| k8s | ||
| .gitignore | ||
| Dockerfile | ||
| LICENSE | ||
| package-lock.json | ||
| package.json | ||