Skip to main content
Internal page, restricted to project members. Back to the internal index.
This page lists known defects and hardening items from the core backlog and the module reviews, plus findings recorded while Yukta ran its own checks. It covers bugs only; feature ideas are on the improvements page. Modules with no items are not listed. Severity uses the scale of the source: High, Medium and Low from the remediation plan, and P0 (fix now) to P3 (clean-up) from the module reviews; “Not rated” means the source gives none. Where the core backlog and the later remediation plan disagree, the later and more recently verified status is used. Status is one of Open, Fixed, Dropped (not planned) or Not a defect (re-verification found nothing wrong). Fixed items stay listed so the history of an id is not lost. Eight review findings of the plugins module (G10, G12, G15, G16, G20, G21, G22, G24) were not re-checked in 2026-10-15 and are on the improvements page instead.

​
Summary

​
Build logic

​
CLI

​
Core

​
Dogfood findings

Defects, errors and slowdowns noticed while Yukta ran its own checks (the dogfood loop). Set the status when one is fixed.

​
DF-5: the long-running server on :8080 died during a --watch run

  • Status: open (not reproduced)
  • Severity: P2
  • Kind: error
  • Found: 2026-10-13, workflow quick-check, execution f44043ba-1735-4b47-b093-826c7f3ced92
  • Evidence: after yukta controlbus watch failed with unexpected EOF, localhost:8080 refused connections and the process was gone. No log was captured because the server was started from a terminal.
  • Repro: unknown.
  • Update 2026-10-14: not reproduced. A native server on port 9101 survived two full gradle-check runs plus watchers after the DF-3 fix (it died only while DF-3 broke the stream). Native servers now log to .yukta-dev/<name>.log. Reopen with that log if it recurs; the suspect remains the old native build.
The module guide is core.

​
Plugins

The module guide is plugins.

​
Recording a dogfood finding

When a dogfood run (a watched run of Yukta’s own checks) shows a Yukta defect, record it on this page instead of in a file next to the code.
  1. Find the module’s section on this page and its ### Dogfood findings heading. If the module has no section yet, add ## <Module> in alphabetical position with that heading. Defects in the dogfood scripts and workflows themselves go under a ## Dogfood tooling section.
  2. Use the next unused DF-<n> across the whole page (the ids are not per module) and add an entry:
  1. Add a row for it to the summary table at the top of the page so it is counted.
This page is MDX: put commands and log lines in backticks, and escape {, } and < outside code.