TiinyBench 0.1.2

Two testers reported the same thing in different words, and it was one cause: the page never ran.

The confirm dialog added in 0.1.1 sat above the script's own scope and called $ on its first line, so the whole <script> stopped on a ReferenceError before it asked for anything. Nothing below it executed. No navigation, no request for the device, no find button. The app came up looking finished with every control dead, on Windows and on a Mac alike.

Fixed in this release

• The page runs. Connection opens, the find button finds, the dashboard fills in.
• Discovery works on Windows. It used to shell out to ip and then ifconfig, and Windows has neither, so the candidate list was empty and a Tiiny on the same network could not be found. It is stdlib now and the same on every platform.
• The scan asks the responder the farm CLI asks, a GADGET_DISCOVER_V1 datagram on port 39217, which is the only probe that finds a box whose address moved.
• The Connection panel says what it is doing. It paints "Looking for your Tiiny" before the first request leaves, says so plainly when nothing answers, and offers the address box and the key box either way.
• The dashboard no longer dies on a fresh install. Asking for the leaderboard without a key was dropping the connection.
• tiiny-bench --where prints what it looked for and exits cleanly when there is no Tiiny attached.
• At 390 pixels wide the navigation used to push every panel off the right edge behind a sideways scroll.
• Text files are read and written as UTF-8 everywhere, so the report comes out right on Windows.

New

Continuous integration on Linux, macOS and Windows, with 28 unit tests. None of it needs a Tiiny.

A Tiiny on a different network is still reached by typing its address into the Connection panel. A discovery datagram does not cross a router, and the panel now says so.