Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
T
Tidal
  • Overview
    • Overview
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • PLN
  • Tidal
  • Repository

Switch branch/tag
  • Tidal
  • tools
  • foundry
  • ui
  • index.html
Find file
BlameHistoryPermalink
  • PLN (Algolia)'s avatar
    foundry, check-mix: say who actually heard what, and stop one mode lying · 084e692b
    66318b6e's comment and test docstring both claimed PLN heard the polled-loop
    stutter. He did not. The Foundry server was not running: port 8765 was
    another project's http.server, established two steps after the fix landed.
    The bug is real and of exactly the reported shape, and it stays fixed - but
    attributing a fix to a symptom it did not cause is how a wrong diagnosis
    becomes documentation, which is this morning's -inf-faders mistake again.
    Both places now say where it came from. The commit message is history and is
    left alone.
    
    And check-mix's --arm table called an unarmed `Mix` route "not recorded, by
    choice" while --mix blocks on precisely that. Two modes of one tool must not
    disagree about the same route.
    PLN (Algolia) authored Sep 25, 2026
    084e692b
index.html 22.7 KB
EditWeb IDE
×

Replace index.html

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.