|
@@ -24,6 +24,7 @@ All notable changes to Bambuddy will be documented in this file.
|
|
|
- **"Any model" jobs go to the printer with the fewest print hours (#3480, sponsor vote Q4 2026)** — When several printers of a model can take a job, the queue used to pick the first one in its list, so on a farm the same printer got most of the work. It now picks the one with the fewest print hours (the Maintenance counter, including baseline hours entered there), so jobs and wear spread across the farm. Preferred colours still come first, and the queue powers on the least used printer too when it has to switch one on with an Auto Power On plug.
|
|
- **"Any model" jobs go to the printer with the fewest print hours (#3480, sponsor vote Q4 2026)** — When several printers of a model can take a job, the queue used to pick the first one in its list, so on a farm the same printer got most of the work. It now picks the one with the fewest print hours (the Maintenance counter, including baseline hours entered there), so jobs and wear spread across the farm. Preferred colours still come first, and the queue powers on the least used printer too when it has to switch one on with an Auto Power On plug.
|
|
|
|
|
|
|
|
### Fixed
|
|
### Fixed
|
|
|
|
|
+- **The spool CSV import reads files saved by Excel with European regional settings (#3523, reported and fixed by @jayhemnani9910 in #3529)** — Excel in a comma-decimal locale (German, French, Dutch, Italian, ...) saves CSV with `;` between the fields and `,` as the decimal mark. The import only read commas, so the whole header became one unknown column and nothing was imported ("Required column 'material' is missing"). The separator is now taken from the header line, and in a `;` file a decimal comma in `cost_per_kg` and `weight_used` is read as a decimal point, so `24,99` imports as 24.99. Comma-separated files are read as before. Wiki updated.
|
|
|
- **Long uploads to an A1 no longer end in a failed or unreadable print (#3538, reported by @SaadShaya7)** — Two problems at the handoff from a slow upload to the print command, seen with a 19 MB file that took three minutes. When the printer didn't confirm the upload, Bambuddy read the file size back, logged that the file was incomplete, and sent the print command anyway: the printer was still writing the file and either stayed idle or reported that it could not parse it. Bambuddy now keeps reading the size for up to two minutes, sends the print command once the file is complete, and otherwise retries the upload. And because the A1 sends no status while it receives a file, Bambuddy took the silence for a dead connection and reconnected just before the print command, which then failed the job. Silence during an upload, and in the minute after it, no longer counts as a dead connection; this also applies to firmware uploads.
|
|
- **Long uploads to an A1 no longer end in a failed or unreadable print (#3538, reported by @SaadShaya7)** — Two problems at the handoff from a slow upload to the print command, seen with a 19 MB file that took three minutes. When the printer didn't confirm the upload, Bambuddy read the file size back, logged that the file was incomplete, and sent the print command anyway: the printer was still writing the file and either stayed idle or reported that it could not parse it. Bambuddy now keeps reading the size for up to two minutes, sends the print command once the file is complete, and otherwise retries the upload. And because the A1 sends no status while it receives a file, Bambuddy took the silence for a dead connection and reconnected just before the print command, which then failed the job. Silence during an upload, and in the minute after it, no longer counts as a dead connection; this also applies to firmware uploads.
|
|
|
- **A failed slice for another printer is reported as failed (#3535, reported by @Jesse-Cachai)** — When the slicer failed on a 3MF with the picked printer, process and filament profiles, Bambuddy retried with the settings saved in the file and reported the slice as completed. Those settings are for the printer the file was made for, so a P1S project sliced for another printer came back as P1S G-code, with a believable print time and filament estimate. The retry now runs only when the file was made for the picked printer. For any other printer, or when either printer can't be told from the file or the profile, the slice fails with the slicer's error.
|
|
- **A failed slice for another printer is reported as failed (#3535, reported by @Jesse-Cachai)** — When the slicer failed on a 3MF with the picked printer, process and filament profiles, Bambuddy retried with the settings saved in the file and reported the slice as completed. Those settings are for the printer the file was made for, so a P1S project sliced for another printer came back as P1S G-code, with a believable print time and filament estimate. The retry now runs only when the file was made for the picked printer. For any other printer, or when either printer can't be told from the file or the profile, the slice fails with the slicer's error.
|
|
|
- **A user moved out of Administrators is no longer an admin (#3533)** — Users carry an older admin role next to their groups, and either one made them an admin. The account created during setup has both, so moving it from Administrators to Operators left it with every admin right, still showing the Admin badge, and the user settings had no way to remove the role. The groups now decide: the role follows them wherever they change, in the user settings, on the groups, through the API and at LDAP or OIDC sign-in. Removing the last admin from Administrators is refused, as deactivating them already was. On the first start after the update, users who are not in Administrators lose the old admin role. If they are the only admins, they are added to Administrators instead.
|
|
- **A user moved out of Administrators is no longer an admin (#3533)** — Users carry an older admin role next to their groups, and either one made them an admin. The account created during setup has both, so moving it from Administrators to Operators left it with every admin right, still showing the Admin badge, and the user settings had no way to remove the role. The groups now decide: the role follows them wherever they change, in the user settings, on the groups, through the API and at LDAP or OIDC sign-in. Removing the last admin from Administrators is refused, as deactivating them already was. On the first start after the update, users who are not in Administrators lose the old admin role. If they are the only admins, they are added to Administrators instead.
|