Bugs found while running this stack get filed and patched at the source. Each entry below is a real contribution to a real open-source project, with a link to the upstream issue or PR and the blog post that documents the diagnosis. The same engineering log that powers this blog also produces these. Identity for all of these: github.com/cipherfoxie.
Snapshot from GitHub API on 2026-05-06. Refreshed each deploy.
Listed the Sovereign AI MCP under Knowledge & Memory in the canonical awesome-mcp-servers index. Part of a four-registry distribution push (Smithery, Glama Connector, Glama Server, awesome-mcp) executed in a single afternoon. Merged within hours of submission.
Issue #215 (filed 2024-05-06) flagged that the README's documented pattern for assigning the provider to window.webln in onConnected leaves a stale provider on the global after disconnect — the saved reference outlives the wallet connection. Library can't own window.webln (would conflict with consumer expectations + other extensions), so the right fix is documentation. PR extends the WebLN global object example to pair onConnected with onDisconnected and delete the global.
Re-submission of vite-plugin-pwa #930 after maintainer @userquin closed the original (wrong-repo: docs moved to this dedicated repository). The same 'Will coming soon' typo found in deployment/aws.md — 'will' takes a bare infinitive, not a present participle. 1-line fix to 'Coming soon'. Two-step engagement pattern: (1) initial PR in wrong repo, (2) maintainer redirects, (3) re-submit cleanly + offer follow-up cleanup of orphan placeholder files in the legacy repo.
OpenClaw's request shape produces consecutive user messages in normal multi-turn flows, which Mistral's strict-alternation chat template rejects with HTTP 400. Today this requires an external side-car proxy. Filed as a feature request with two suggested in-repo approaches (provider capability flag, or pre-send hook on the Mistral plugin) and an offer to draft the PR.
AgentController._handle_message_action dispatches a RecallAction with EventSource.USER after every user message. The recall lands as a synthetic USER turn, so the LLM request carries two consecutive user messages and any Mistral-template-strict backend rejects it with HTTP 400 on prompt 1 of every session. Three suggested fixes plus the controller-patch workaround that operators run today.
Under context pressure the model emits a partial-rewrite that drops chunks of the original file, but the tool-call success shape is unchanged so the write commits silently. Suggested handling: pre-commit size-delta check, an apply_patch primitive bounded to the section being edited, and a context-overflow flag that an MCP can refuse on.
OpenAIAdapter._parse_message rejected streaming chunks 2+ because delta.role is null per OpenAI spec but LLMMessage.role is a required enum without default. TUI failed on the first user prompt of every session. Three-line defensive default, plus a suggestion for a cleaner upstream form (Optional role with default).
Reproduction with raw SGLang chunk dump, two falsified hypotheses (a 2.9.3 streaming-parser regression and a Pydantic 2.13 enum-strictness change) before the actual root cause was traced to _parse_message.
Cross-pollination comment from adjacent inference engines on the same DGX Spark / GB10 hardware: SGLang nightly with Mistral Small 4 NVFP4 + vLLM for Voxtral. Pointed maintainers to sibling sgl-project/sglang#21085 and the two open SGLang PRs attempting fixes (#21558, #24269). Reinforced @EmilHaase's finding that native causal-conv1d works on SM121 but Triton-generated equivalents fail — the bug is in the Triton-codegen-for-SM121 path specifically, not the substrate. Offered to test the CUDA_LAUNCH_BLOCKING=1 + --enforce-eager workaround on this Spark and cross-check whether vLLM's Triton SSM ops fail the same way SGLang's flashinfer-GDN path does. Asked for a minimal Mamba-2 repro that avoids the 120B Nemotron-3 weights.
Closed by maintainer @userquin: the framework docs pages in this repository are orphan placeholders, the canonical docs moved to vite-pwa/docs. PR re-submitted there as #192. While engaging on the close, I asked the maintainer whether the orphan files (astro.md + iles.md, both <12 lines) should be removed entirely from this repo to prevent search-engine landings on stale content. Engagement model worked even on a closed PR: same-day maintainer response, helpful redirect, opening for follow-up cleanup PR.
Bitcoin Connect listens to the webln:enabled event in boot.ts to detect external WebLN providers, but never dispatches it itself when one of its own connectors finishes connecting. PR dispatched the event after a successful connect in store.ts and tightened the listener guard in boot.ts. Closed by maintainer rolznz on 2026-05-06 with a design clarification: BC deliberately does not own window.webln, consumers manage the provider locally via onConnected, so firing the global event would mislead spec-following callers that read window.webln directly. Useful outcome anyway — the closure surfaced the documented ownership model and led to companion docs PR #385.
No contributions match the current filter.
Every fix that ships in production here started as a bug somewhere upstream. Sending the fix back is the honest move and produces a more durable record than a private patch. This page is also the consolidated public-facing index of contributions, easier than scrolling GitHub profile activity.
If a contribution is open and you have an interest in it landing, react on the GitHub issue or PR directly. The blog posts give the engineering context, the upstream tracker is where the merge decision happens.