bambuddy

3,002 Commits 82 Branches 83 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
maziggy	b23cb69a66	fix(permissions): self-heal Administrators to ALL_PERMISSIONS on upgrade + Pipelines runs dashboard polish Administrators system group sync - Fresh installs already bootstrap with ALL_PERMISSIONS, so they always have every permission. Upgrades previously only got what one-off backfill blocks in seed_default_groups() explicitly listed (library:purge, archives:purge, the OWN/ALL read-flag block, orca_cloud:auth, pipelines:). Any Permission enum member added without a matching block silently stayed missing on existing admin rows. The most recent gap was printer_sensor_history:read (Sensor History charts returned 403 for upgraded admins). - seed_default_groups() now syncs Administrators to ALL_PERMISSIONS on every startup: append every Permission value that isn't already on the row. Additive only -- hand-added custom permissions are preserved. - The pure-admin one-off backfills (library:purge / archives:purge block, the OWN/ALL + orca_cloud:auth + legacy-read-flag block, the Administrators branch of the pipeline backfill) are retired since the sync subsumes them. Non-admin backfills (Operators / Viewers OWN-tier reads, Operators orca_cloud:auth, pipelines for non-admin groups, makerworld:, clear_plate cross-group adders) are untouched. - Tests: test_administrators_printer_sensor_history_read_backfilled (regression for the reported gap), test_administrators_sync_covers_every_current_permission (generic invariant -- any future new permission lands on admin without needing a one-off test), test_administrators_sync_is_additive_only (custom permissions preserved). 12/12 backfill-migration + 102/102 broader permission tests green; ruff clean. Pipelines runs dashboard - PipelineRunsPage.tsx: the Pipeline / Status / Target filter row's three native <select> elements are replaced with a bambu-themed FilterDropdown (button trigger, floating menu, optgroup-style headers for the Target picker, hover + selected states with a check mark, closes on outside click and Escape). Same value/onChange contract -- visual only. - SlicerPipelinesPanel.tsx: wrap list?.pipelines ?? [] in useMemo so the reference is stable when the data is stable. Fixes the react-hooks/exhaustive-deps warning where the inline fallback returned a fresh empty array every render, invalidating both downstream useMemo caches (target-options + filtered-pipelines list).	2026-06-28 11:18:18 +02:00
maziggy	3ef197e4e0	feat(slicer): Pipelines — multi-copy + class targeting + fanout + runs dashboard + retry-failed + WS updates (#1425 PR C — completes the v3 design) PR A/B turned the slice modal's preset bundle into a one-click dispatch with a pinned target printer. PR C closes the original issue: operators type in a number of copies, Bambuddy slices once and distributes prints across a fleet per the pipeline's chosen fanout strategy. A new dashboard surfaces every run with filters, expandable per-copy status, cancel, and retry-failed-copies. WS pushes keep everything live. Backend - copies field on POST /run, capped by new pipeline_max_copies setting (default 50, hard cap 1000). PipelineRun.parent_run_id chains retries. - SlicerPipelineUpdate accepts target_kind (specific_printer / printer_class), target_model_class, fanout_strategy. - Eligibility matcher branches: class-targeting enumerates matching Printer rows, runs per-printer checks via a status_lookup closure, returns printer_reports[]. New issue kinds: no_class_matches, class_not_set. - _pick_assignments distributes copies per strategy: - max_parallel: target_model set, printer_id None — scheduler picks - round_robin: copy i → eligible[i % N], fixed printer_id - fill_one_first: all copies pinned to eligible[0] All three reuse the slice-once path through slice_dispatch.enqueue. - New routes: - GET /pipeline-runs (paginated, filterable by pipeline + status) - POST /pipeline-runs/{id}/retry-failed (creates child run with copies = failed+cancelled count, parent_run_id set) - Cancel cascades to all N queue entries (only pending/queued) - _roll_up_run_status computes run-level status from per-job statuses; introduces partial_failure for "some completed, some failed". - ws_manager.broadcast_to_user emits pipeline_run_updated on every state transition with the full materialised response. Frontend - Pipeline editor: target_kind radio + class picker (filtered to installed models) + fanout-strategy radio. Read-only row shows "X1C · Round robin" for class pipelines. - RunWithPipelineModal: copies number input bounded by settings.pipeline_max_copies. Accepts class-targeted pipelines. - Settings → Workflow → Queue & Dispatch: new "Slicer Pipeline limits" card with the max-copies input. - New /pipelines/runs dashboard page (sidebar entry, gated on pipelines:read). Two-filter dropdown, 25-per-page pagination, per-row expandable to job list, Cancel + Retry-failed buttons. - useWebSocket case for pipeline_run_updated invalidates both pipeline-runs-all and pipeline-runs/{id} query keys.	2026-06-27 16:52:05 +02:00
maziggy	4bbf0f031e	feat(slicer): Pipelines — archive entry point + slicer progress toast (#1425 PR B follow-up) Two real gaps from the PR B drop: 1. Run-with-pipeline only existed in the file manager. Operators who keep working files in archives had to copy them to the library to use a pipeline. 2. Triggering a slice via a pipeline produced a silent multi-second-to- minute wait. The manual SliceModal flow shows the sticky "Slicing X - Generating G-code 75%" persistent toast; the pipeline path went through asyncio.create_task directly and never registered with SliceJobTracker. Archive entry point - POST /slicer-pipelines/{id}/check-eligibility and /run accept source_archive_id as an alternative to source_library_file_id (XOR, enforced by Pydantic validator). - PipelineRun.source_archive_id is a new nullable FK column with the ALTER TABLE migration in run_migrations (idempotent via _safe_execute, works on SQLite + Postgres). - _resolve_source branches: archive path reads source_3mf_path with fallback to file_path, mirroring routes/archives.py. - ArchiveCard's context menu picks up a "Run with pipeline" item next to Slice (only on source archives), gated on useSlicerApi + pipelines:run. Slice (only on source archives), gated on useSlicerApi + pipelines:run. - Path-safety: SEC-PATH-OK markers added at both LibraryFile.file_path and archive.source_3mf_path join sites, citing the upload-time validators. Progress toast - Pipeline orchestration is now the `run` callable of a slice_dispatch.enqueue call — the same dispatcher SliceModal uses — instead of a bare asyncio.create_task. The SliceJob lifecycle drives the existing progress toast end to end with no separate notification surface for pipeline runs. - PipelineRun.slice_job_id is set before the 202 returns. - RunWithPipelineModal calls useSliceJobTracker().trackJob() from runMutation.onSuccess. - RunWithPipelineModal source prop is now {kind, id, filename} mirroring SliceModal.SliceSource; api.checkPipelineEligibility + api.runPipeline take a discriminated-union source argument.	2026-06-27 15:01:14 +02:00

Author

SHA1

Message

Date

maziggy

b23cb69a66

fix(permissions): self-heal Administrators to ALL_PERMISSIONS on upgrade + Pipelines runs dashboard polish

Administrators system group sync
- Fresh installs already bootstrap with ALL_PERMISSIONS, so they always have
  every permission. Upgrades previously only got what one-off backfill blocks
  in seed_default_groups() explicitly listed (library:purge, archives:purge,
  the OWN/ALL read-flag block, orca_cloud:auth, pipelines:*). Any Permission
  enum member added without a matching block silently stayed missing on
  existing admin rows. The most recent gap was printer_sensor_history:read
  (Sensor History charts returned 403 for upgraded admins).
- seed_default_groups() now syncs Administrators to ALL_PERMISSIONS on every
  startup: append every Permission value that isn't already on the row.
  Additive only -- hand-added custom permissions are preserved.
- The pure-admin one-off backfills (library:purge / archives:purge block,
  the OWN/ALL + orca_cloud:auth + legacy-read-flag block, the Administrators
  branch of the pipeline backfill) are retired since the sync subsumes
  them. Non-admin backfills (Operators / Viewers OWN-tier reads, Operators
  orca_cloud:auth, pipelines for non-admin groups, makerworld:*, clear_plate
  cross-group adders) are untouched.
- Tests: test_administrators_printer_sensor_history_read_backfilled
  (regression for the reported gap),
  test_administrators_sync_covers_every_current_permission (generic
  invariant -- any future new permission lands on admin without needing
  a one-off test), test_administrators_sync_is_additive_only (custom
  permissions preserved). 12/12 backfill-migration + 102/102 broader
  permission tests green; ruff clean.

Pipelines runs dashboard
- PipelineRunsPage.tsx: the Pipeline / Status / Target filter row's three
  native <select> elements are replaced with a bambu-themed FilterDropdown
  (button trigger, floating menu, optgroup-style headers for the Target
  picker, hover + selected states with a check mark, closes on outside
  click and Escape). Same value/onChange contract -- visual only.
- SlicerPipelinesPanel.tsx: wrap list?.pipelines ?? [] in useMemo so the
  reference is stable when the data is stable. Fixes the
  react-hooks/exhaustive-deps warning where the inline fallback returned
  a fresh empty array every render, invalidating both downstream useMemo
  caches (target-options + filtered-pipelines list).

2026-06-28 11:18:18 +02:00

maziggy

3ef197e4e0

feat(slicer): Pipelines — multi-copy + class targeting + fanout + runs dashboard + retry-failed + WS updates (#1425 PR C — completes the v3 design)

PR A/B turned the slice modal's preset bundle into a one-click dispatch
with a pinned target printer. PR C closes the original issue: operators
type in a number of copies, Bambuddy slices once and distributes prints
across a fleet per the pipeline's chosen fanout strategy. A new dashboard
surfaces every run with filters, expandable per-copy status, cancel,
and retry-failed-copies. WS pushes keep everything live.

Backend
- copies field on POST /run, capped by new pipeline_max_copies setting
  (default 50, hard cap 1000). PipelineRun.parent_run_id chains retries.
- SlicerPipelineUpdate accepts target_kind (specific_printer /
  printer_class), target_model_class, fanout_strategy.
- Eligibility matcher branches: class-targeting enumerates matching
  Printer rows, runs per-printer checks via a status_lookup closure,
  returns printer_reports[]. New issue kinds: no_class_matches,
  class_not_set.
- _pick_assignments distributes copies per strategy:
  - max_parallel: target_model set, printer_id None — scheduler picks
  - round_robin: copy i → eligible[i % N], fixed printer_id
  - fill_one_first: all copies pinned to eligible[0]
  All three reuse the slice-once path through slice_dispatch.enqueue.
- New routes:
  - GET /pipeline-runs (paginated, filterable by pipeline + status)
  - POST /pipeline-runs/{id}/retry-failed (creates child run with
    copies = failed+cancelled count, parent_run_id set)
  - Cancel cascades to all N queue entries (only pending/queued)
- _roll_up_run_status computes run-level status from per-job statuses;
  introduces partial_failure for "some completed, some failed".
- ws_manager.broadcast_to_user emits pipeline_run_updated on every
  state transition with the full materialised response.

Frontend
- Pipeline editor: target_kind radio + class picker (filtered to
  installed models) + fanout-strategy radio. Read-only row shows
  "X1C · Round robin" for class pipelines.
- RunWithPipelineModal: copies number input bounded by
  settings.pipeline_max_copies. Accepts class-targeted pipelines.
- Settings → Workflow → Queue & Dispatch: new "Slicer Pipeline limits"
  card with the max-copies input.
- New /pipelines/runs dashboard page (sidebar entry, gated on
  pipelines:read). Two-filter dropdown, 25-per-page pagination, per-row
  expandable to job list, Cancel + Retry-failed buttons.
- useWebSocket case for pipeline_run_updated invalidates both
  pipeline-runs-all and pipeline-runs/{id} query keys.

2026-06-27 16:52:05 +02:00

maziggy

4bbf0f031e

feat(slicer): Pipelines — archive entry point + slicer progress toast (#1425 PR B follow-up)

Two real gaps from the PR B drop:

1. Run-with-pipeline only existed in the file manager. Operators who keep
   working files in archives had to copy them to the library to use a
   pipeline.

2. Triggering a slice via a pipeline produced a silent multi-second-to-
   minute wait. The manual SliceModal flow shows the sticky
   "Slicing X - Generating G-code 75%" persistent toast; the pipeline
   path went through asyncio.create_task directly and never registered
   with SliceJobTracker.

Archive entry point
- POST /slicer-pipelines/{id}/check-eligibility and /run accept
  source_archive_id as an alternative to source_library_file_id (XOR,
  enforced by Pydantic validator).
- PipelineRun.source_archive_id is a new nullable FK column with the
  ALTER TABLE migration in run_migrations (idempotent via _safe_execute,
  works on SQLite + Postgres).
- _resolve_source branches: archive path reads source_3mf_path with
  fallback to file_path, mirroring routes/archives.py.
- ArchiveCard's context menu picks up a "Run with pipeline" item next to
  Slice (only on source archives), gated on useSlicerApi + pipelines:run.
  Slice (only on source archives), gated on useSlicerApi + pipelines:run.
- Path-safety: SEC-PATH-OK markers added at both LibraryFile.file_path
  and archive.source_3mf_path join sites, citing the upload-time
  validators.

Progress toast
- Pipeline orchestration is now the `run` callable of a
  slice_dispatch.enqueue call — the same dispatcher SliceModal uses —
  instead of a bare asyncio.create_task. The SliceJob lifecycle drives
  the existing progress toast end to end with no separate notification
  surface for pipeline runs.
- PipelineRun.slice_job_id is set before the 202 returns.
- RunWithPipelineModal calls useSliceJobTracker().trackJob() from
  runMutation.onSuccess.
- RunWithPipelineModal source prop is now {kind, id, filename}
  mirroring SliceModal.SliceSource; api.checkPipelineEligibility +
  api.runPipeline take a discriminated-union source argument.

2026-06-27 15:01:14 +02:00