fix: add shared API pagination and failure handling (#67) #83
No Reviewers
Labels
Clear labels
allocator
anti-stomp
architecture
bug
chore
codex
concurrency
contamination
control-plane
dashboard
database
design
documentation
enhancement
gitea
glitchtip
important
incident
incident-bridge
integration
jenkins
labels
leases
mcp
mcp-health
mcp-menu
multi-project
mutating
nice-to-have
observability
portability
preflight
protected-branch
queue
read-only
reconnect
recovery
refactor
release
reliability
resumable-review
reviewer
roadmap
safety
security
self-hosted
sentry
stale-runtime
status:blocked
status:in-progress
status:pr-open
status:ready
terminal-lock
testing
tracker
type:bug
type:feature
type:feature
type:guardrail
visibility
workflow
workflow-hardening
workflow-hardening
Controller-owned work allocator
Prevent concurrent LLM session stomping
Architecture / structural design
OpenAI Codex client / workflow session surface
Concurrent session safety
Workflow or session contamination incident
MCP control-plane coordination and allocation authority
MCP operational dashboard/queue view
Internal coordination storage (SQLite/Postgres)
Design / investigation, no implementation
Docs / runbooks
New feature or improvement
Gitea MCP workflow
GlitchTip integration
Operational or process incident requiring durable audit trail
Sentry-to-Gitea incident bridging
Integration testing
Jenkins integration
Label taxonomy management
Lease adopt/release/expire lifecycle
MCP server / tooling
MCP namespace and runtime health
MCP menu surface
Work spanning multiple monitoring projects or Gitea repos
Mutating action; requires gating
Observability, metrics, traces, error reporting
Cross-platform / portability
Shared preflight gates before mutation
Protected branch / stable-branch policy concern
Work queue visibility and allocation
Read-only, no mutation
MCP client reconnect/reload recovery path
Recovery paths for stale/foreign leases
Code refactor / restructure
Release / versioning
Reliability / failure handling
Persist and resume prepared review verdicts across sessions
Reviewer workflow tooling
Roadmap / umbrella issue
Safety rails and fail-closed mutation guards
Security / trust boundary
Self-hosted infrastructure integration
Sentry error monitoring integration
Stale backend daemon / runtime-vs-master parity failures
Issue is blocked
Issue is being worked on
Issue has an open pull request
Issue is ready for work
Terminal review lock (#332) path
Tests / test coverage
Issue tracker hygiene / meta
Bug or defect
Feature or enhancement
Feature or enhancement
Safety gate or guardrail
Workflow state visibility for LLMs/operators
Cross-tool workflow
LLM workflow coordination hardening
LLM workflow coordination hardening
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Scaled-Tech-Consulting/Gitea-Tools#83
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Implements #67. Narrow API-reliability improvement with unit coverage — no
mcp_server.pymodular refactor (#65).Reliability gap
gitea_auth.api_requesthad no request timeout, letURLError/timeouts/DNS failures propagate raw (uncaught), gave 502/503 no clarity, raised bareJSONDecodeErroron malformed success bodies, echoed raw upstream error bodies unredacted, and did no pagination (one page only —gitea_list_issueseven crashed on aNonebody).Changes
gitea_auth.pyapi_requesthardened: per-requesttimeout(envGITEA_HTTP_TIMEOUT, default 30s);(URLError, TimeoutError)→ clearRuntimeError("network error contacting Gitea: …"); 502/503/504 → explicit "Gitea upstream unavailable"; malformed success JSON →RuntimeError("malformed JSON response…"); all error text redacted via the audit redactor. Success path and 429 retry/backoff preserved.api_get_all(url, auth, *, limit=None, page_size=50, max_pages=100): page-based pagination that relies on page length (tolerates missing/malformedX-Total-Count/Linkmetadata), honors an optional overalllimit, and caps pages. Reusesapi_request(inherits failure handling).mcp_server.py— wiredapi_get_allinto read-only list toolsgitea_list_issues,gitea_list_prs,gitea_list_labels. Return shapes unchanged;list_issuesstill honorslimitas an overall max, now across pages. Internal?limit=100label-id lookups left unchanged (out of scope; noted follow-up).Tests
tests/test_api_reliability.py— 18 cases: single/multi-page, missing metadata, malformed (non-list) metadata, limit cap, max-pages cap, query preservation; timeout, DNS/network, 502/503, malformed error payload, malformed success JSON, no-secret leakage, auth-header-never-in-error, success + 429 preserved.test_mcp_server.pyto the new call path.Checks
py_compile mcp_server.py/manage_labels.py(+gitea_auth.py) — OKbash -n scripts/clear-provenance— OKgit diff --check— cleanpytest tests/ -q— 345 passed (327 → +18)Scope
No auth/profile/merge/review/tracker behavior changed. No Jenkins/GlitchTip/release/worktree changes. No #65 refactor.
🤖 Generated with Claude Code
Reviewed PR #83 at
cfe3ff6755. Scope is limited to shared Gitea API reliability/pagination handling and tests. Changed files match expected, pagination is wired only into list PRs/issues/labels, targeted and full test suites pass, and no auth/profile/merge/review/tracker behavior or Jenkins/GlitchTip work is included.