-
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
[P3] _format_escalation_comment is shared by 4 distinct parking paths but does not record which one fired, so triage cannot tell them apart
auditAudit finding or follow-upAudit finding or follow-uppriority/p3Low priorityLow priorityStatus: Open.#260 In misospace/foreman-dispatch-bridge;[P3] AGENT_NAME_ANNOTATION is stamped on every Workload but no code path reads it; the leading comment is also misleading
auditAudit finding or follow-upAudit finding or follow-uppriority/p3Low priorityLow priorityStatus: Open.#259 In misospace/foreman-dispatch-bridge;[P3] workload_name lowercases the repo full name so Org/Repo and org/Repo collide on one Workload name
auditAudit finding or follow-upAudit finding or follow-uppriority/p3Low priorityLow priorityStatus: Open.#258 In misospace/foreman-dispatch-bridge;[P2] All nine kubernetes CustomObjectsApi calls in bridge/main.py are unwrapped — a transient ApiException 5xx aborts the tick
auditAudit finding or follow-upAudit finding or follow-upStatus: Open.#257 In misospace/foreman-dispatch-bridge;[P3] Dockerfile TEMPORARY OS-package patch layer has silently grown past its documented scope
auditAudit finding or follow-upAudit finding or follow-uppriority/p3Low priorityLow priorityStatus: Open.#254 In misospace/foreman-dispatch-bridge;[P3] README DISPATCH_AGENT_NAME row contradicts itself: default uses a slash while the description says use a dash
auditAudit finding or follow-upAudit finding or follow-uppriority/p3Low priorityLow priorityStatus: Open.#253 In misospace/foreman-dispatch-bridge;- Status: Open.#7 In misospace/foreman-dispatch-bridge;