Back to Downloads

Nightly update: transmute execution, path streaming, and less log noise

This nightly focuses on a set of real workflow fixes around Transmute, especially for folders, sequence-style paths, and path discovery in the machine picker.

What changed

  • Fixed a folder-transmute execution failure where some valid sequence-shaped paths could be selected in the UI but then fail during task creation.

    • Structural ForEach edges are now treated correctly when resolving runtime output media.
    • Real multi-input ambiguity still fails hard; only the false structural ambiguity was removed.
  • Improved content-analysis errors for mixed selections.

    • If a selected set of files or folders does not resolve to a single common source type, the app now says that plainly.
    • This is now returned as a user-facing precondition/input error, not as an internal server error.
  • Improved streaming of available transmute paths in the machine picker.

    • The first result is delivered immediately in a batch of 1.
    • Later batches grow dynamically: 1, 2, 4, 8, ...
    • Batch growth is capped, and a timeout guard flushes partial batches so streaming does not stall waiting for the next full threshold.
  • Fixed folder access prompts so they target the right directory.

    • File-based imports now ask for the containing folder itself.
    • Folder-based imports now ask for the selected folder from its parent directory.
    • This removes the previous “one level too high” access prompt.
  • Reduced low-signal logging noise.

    • Removed repeated GraphViewer payload dumps.
    • Removed per-row cartridge inventory spam from installed-cartridge refreshes.
    • Rate-limited repeated heartbeat and relay-disconnect logs so the logs keep state changes and real errors without flooding.

Why it matters

  • Folder and sequence-driven transmutes are more reliable.
  • Mixed selections now fail with an actionable explanation instead of looking like a backend crash.
  • Available paths should start appearing sooner in the machine picker.
  • Logs are easier to read because they carry more signal and less repetition.

Notes

  • This is a nightly build intended for testing and feedback.
  • The main behavioral focus of this build is transmute correctness and responsiveness, not new end-user surface area.

Feedback