Repository navigation
Tags: tangosdev/tangOS
Tags
Release 3.4.7: setup problems come with buttons, not a traceback Pressing Go on a repo that was not set up ran the scheduler, waited for it to die, and showed the crash in a dialog that could only tell you to go run a command yourself. Console now checks first. The function data it can fetch or rebuild, it just fixes, without mentioning it. The ROM it cannot invent, but the requirements panel now has a button that opens a file picker and extracts the dump you choose, and there are working buttons for Python and its packages too. Anything still missing stops Go up front with a calm notice naming it, so the scheduler never runs into a wall.
Release 3.4.6: one Go button per AI, and cards that hold still Starting an AI took two presses and three decisions: a role the app admitted it could not recommend yet, a batch size, a choice between queueing and looping, and then Drive queue as a separate step for API agents. The controller now opens in Simple mode: each AI is a status line and one button that reads Go and turns into Stop, with a count beside it that defaults to matching until you stop it. The role is chosen from what the AI has actually been good at here, then from the model behind it, and failing both it draws from the whole unmatched pool. Advanced mode in Settings brings every old control back. Cards are also a fixed height now, so a progress bar or a stats row appearing mid-run no longer resizes a card and shifts the row you were reading.
Release 3.4.5: contributor colours and the today badge follow the pro… …ject A project the backend does not serve was reading neither cosmetics nor counts, because both were only ever fetched from claimsApi. Its contributors fell back to the local palette, so the same person was one colour in this Atlas and another on sm64ds, and with no counts at all the matches-today arrow had no number to draw and never appeared. Both now resolve through the project's own backend routes when it has no claims API of its own. A bought colour stays with the person across every decomp; the career and today counts come from the decomp on screen.
Release 3.4.4: the Atlas keeps up with merges instead of freezing on … …open The Live view fetched once when it opened and never again. sm64ds got away with it because the backend's SSE feed pushes matched state seconds after a merge, so the tiles moved anyway; a project with no backend had nothing pushing to it at all, and a match merged while the window was up simply never appeared. It now polls while the view is open, and reloads the moment the backend says that project's own CI has published fresh data, which lands about fifteen seconds after a merge. The publish stream comes from the new descriptor field liveApi, kept separate from claimsApi so a project without a backend gets its own notifications and not somebody else's claims, colours and counts.
PreviousNext