-
Notifications
You must be signed in to change notification settings - Fork 0
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
A 2xx batch response that isn't valid JSON, or has a mistyped field, returns 500 instead of 502 (e.g. an SSO page served with 200)
bugSomething isn't workingSomething isn't workingStatus: Open.#81 In ktsu-dev/GitLfsCache;No container image has been published since 2026-08-26: the CI migration dropped the ghcr publish job, but README and deploy/k8s still pull ghcr.io/ktsu-dev/gitlfscache:latest
bugSomething isn't workingSomething isn't workingStatus: Open.#80 In ktsu-dev/GitLfsCache;locks/batchfailure results drop upstream'slockobject, so a 409 conflict no longer says who holds the file, and exhausted retries always report 429enhancementNew feature or requestNew feature or requestStatus: Open.#78 In ktsu-dev/GitLfsCache;POST locks/batchreturns 500 instead of 400 whenrefis not an object (e.g."ref": "refs/heads/main")bugSomething isn't workingSomething isn't workingStatus: Open.#77 In ktsu-dev/GitLfsCache;No bytes-evicted metric: eviction sweeps are only visible in logs (spec instrumentation item missing)
enhancementNew feature or requestNew feature or requestStatus: Open.#75 In ktsu-dev/GitLfsCache;One network error on a single locks/batch item turns the whole fan-out into a 500, discarding locks upstream already granted
bugSomething isn't workingSomething isn't workingStatus: Open.#74 In ktsu-dev/GitLfsCache;A backslash in the request path escapes the upstream base-URL prefix and the repository allow-list
bugSomething isn't workingSomething isn't workingStatus: Open.#73 In ktsu-dev/GitLfsCache;No lock snapshot-size metric: operators can't see how close a repository is to MaxSnapshotLocks (spec instrumentation item missing)
enhancementNew feature or requestNew feature or requestStatus: Open.#72 In ktsu-dev/GitLfsCache;Unlock by path fails with 404/409 when the snapshot names a released-and-reissued lock id: the spec's one refresh + one retry isn't implemented
enhancementNew feature or requestNew feature or requestStatus: Open.#71 In ktsu-dev/GitLfsCache;A lock created or released during an in-flight lock-list refresh is missing from listings for a full ListTtl: the refresh publishes its stale walk after the invalidation ran
bugSomething isn't workingSomething isn't workingStatus: Open.#70 In ktsu-dev/GitLfsCache;A staging flush that fails (e.g. disk full) turns an upload upstream accepted into a 500, and leaves the staging file uncollectable until restart
bugSomething isn't workingSomething isn't workingStatus: Open.#69 In ktsu-dev/GitLfsCache;- Status: Open.#66 In ktsu-dev/GitLfsCache;