Bläddra i källkod

Changelog: 1.3.2 backup entry in its section, release date

maziggy 12 timmar sedan
förälder
incheckning
4f66450d8d
1 ändrade filer med 2 tillägg och 2 borttagningar
  1. 2 2
      CHANGELOG.md

+ 2 - 2
CHANGELOG.md

@@ -2,7 +2,7 @@
 
 All notable changes to Bambuddy will be documented in this file.
 
-## [1.3.2] - Unreleased
+## [1.3.2] - 2026-11-20
 
 ### Added
 - **The MQTT relay's printer status has the door, extruder, filament and HMS errors, and the broker gets a Last Will (#3401, requested by @Tomat0r; #1850, requested by @DingoPD, contributed by @Keybored02 in #3541)** — Home Assistant had to poll REST for these. `bambuddy/printers/{serial}/status` now carries `door_open`, `active_extruder` (which nozzle prints on a dual-nozzle printer), `tray_now`, `ams`, `vt_tray` (the loaded filaments, with their type and colour) and `hms_errors`, in the shape the REST status has. The relay also tells the broker to publish `{"status": "offline"}` on `bambuddy/status` if the connection drops without a clean disconnect, so a crash or a killed container no longer leaves the retained `online` standing, and a printer dropping is published even when a regular update went out less than a second before.
@@ -15,6 +15,7 @@ All notable changes to Bambuddy will be documented in this file.
 - **Choose which printer an "Any model" job takes (#2915, requested by @bryanmahin, contributed by @Keybored02 in #3547)** — Several printers of a model can take an "Any model" job, and the one with the fewest print hours always got it. **Settings > Workflow > Printer Order for Any-Model Jobs** now chooses: the fewest print hours (the default, as before), the most (use up the machines near replacement first), the printer idle the longest (by its last finished print; one that never printed goes first), or the printers' own priority, a number in **Edit Printer** (lowest first, none last). The order only ranks printers that can take the job: a busy, offline or filament-short printer is still passed over, and preferred colours still come first. Powering a printer on with an Auto Power On plug follows the same order.
 
 ### Fixed
+- **Making or restoring a backup no longer freezes Bambuddy** — Unpacking a backup, copying the archive and other folders back, and writing a backup ZIP ran in the part of Bambuddy that answers every page, live update and printer message, so with a large archive folder nothing else happened for half a minute or more. A restore then wrote a long list of thread stack traces starting with "Timeout (0:00:30)!" to the log, although it succeeded. A backup, scheduled or by hand, held up the printers' live status the same way. These steps now run alongside, and Bambuddy keeps responding while they work.
 - **The arm64 Docker image builds its frontend natively** — The arm64 image built its frontend under QEMU emulation, where the build ran for hours or hung. The frontend is the same JavaScript and CSS on every architecture, so it is now built once on the build host; the Python part and the final image are still built for each architecture. Nothing changes for running installs.
 - **The home screen icon has padding, so iOS and Android no longer clip the logo (#3607, contributed by @pietbrauer in #3617)** — Bambuddy's home screen icons were the bare logo on a transparent background, filling it edge to edge. iOS fills transparent pixels with black and rounds the corners itself, so on an iPhone the logo ran into the edges and its corners were cut off. On Android the same images were also the icons the launcher crops to its own shape, so it cut into the logo too. The logo, unchanged, now sits on a dark tile with room around it, and Android gets icons of its own for cropping, with the logo inside the part it always shows. On an iPhone, which keeps the icon it was added with, remove Bambuddy from the Home Screen and add it again to see the new one.
 - **Add and Edit Printer: a corrected value clears the failed connection check, and the access code can be shown (#3624, reported by @balin77)** — When the connection check on save failed, its warning stayed on screen after the IP address, serial number or access code was corrected. The only way to save was **Save anyway**, which saved without checking the corrected value, and the way to check again was **Back**, which did not say so. Changing one of those fields now clears the warning, so the normal button comes back and the next save checks the new values. **Back** is now **Check again**, which runs the check at once, for a printer that has just been switched on; **Save anyway** stays. The access code field has an eye button to show what was typed, hidden by default. Translated in all locales.
@@ -262,7 +263,6 @@ All notable changes to Bambuddy will be documented in this file.
 - **Camera settings have their own tab, and the settings menu is sorted alphabetically** — Camera settings were split across two tabs: external cameras under General, and camera tokens and the Streaming Overlay builder under API Keys. A new **Camera** tab now holds all three: **External Cameras**, **Camera API Tokens** and **Streaming Overlay**. Old links to the tokens or the overlay builder, including `/camera-tokens`, open the Camera tab. API Keys keeps API keys, webhooks, Connected Apps and the API browser, and is no longer shown to a user who may see none of them; before, such a user only went there for their camera tokens, so an API Keys link now opens the Camera tab for them. Settings search finds the Streaming Overlay builder. The settings menu now lists **General** first and the other tabs alphabetically in the interface language. In Connected Apps, the **Add app** button no longer runs past the edge of the card on mid-sized screens, and the Brazilian Portuguese camera button on the printer card reads "Câmera" again instead of "âmera". Wiki updated. Covered by frontend tests.
 
 ### Fixed
-- **Backup: make and restore a backup without freezing the server** - Unpacking a backup, copying the data folders back and writing a backup ZIP ran on the event loop; with a large archive folder the server answered nothing for over 30 s and the loop watchdog dumped every thread's stack during a restore that then succeeded These steps and the SQLite database copy now run in a worker thread; the code is unchanged, only moved into helpers
 - **Obico failure detection scores like Obico, and a resumed print isn't paused again (#3459, reported by @jasoncronje)** — Bambuddy's port of Obico's scoring left out the step that subtracts the long-term average, so whatever the camera always sees (plate texture, labels) added straight into the score, and the configured action ran as soon as that score passed High. The decision is now Obico's own: the score is the smoothed value minus the printer's long-term average, which carries over between prints on the same printer, so a background that is always in view no longer builds up. Between Low and High a slow build-up is not failing. **Notify only** fires at Obico's alert level, while **Pause print** and **Pause and cut power** wait for its pause level, which takes a clearly stronger signal and is now shown in the Status panel. A detection that appears suddenly and stays is still treated as a failure, as in Obico. Pausing a print no longer resets detection, so a print Bambuddy paused is not paused again after you resume it; the next print starts fresh. Wiki updated.
 - **A dropped printer connection no longer replays old commands and cancels the print (#3454, reported and diagnosed by @SaadShaya7)** — When the connection to a printer dropped and came back by itself, every command still waiting for the printer's acknowledgement was sent again. Bambu printers often don't acknowledge, so that could be a Stop or a print start from hours earlier: a print 4 hours in was cancelled seconds after the reconnect, and an old print start raised "Device is busy and cannot start new task". Commands from the previous connection are now dropped when it comes back, also when a printer that was switched off is turned on again, and the log says how many. A command sent in the seconds before a drop isn't sent again; click it once more.
 - **Finish photo: the plate is no longer driven to the bottom after a tall print** — With **Restore plate for finish photo** on, Bambuddy lowered the plate after the photo to the print's height + 100 mm, whatever the printer. On a 238 mm print on an H2C that is Z338, past the bottom of its travel: Bambu's own end G-code stops at the print's height + 2 mm when +100 doesn't fit, and the printer does not stop G-code sent over the network at its limits. The plate now goes back exactly where the print's end G-code left it, read from the archived file, and is only raised for the photo when the end G-code left it lower than just above the print (the H2C's doesn't, so its plate stays put). A file whose end position can't be read is not moved at all. Wiki updated.