maziggy 276a1db3ef fix(dispatch): forward authenticated user through library-print path (#730 follow-up) ...

The 0.2.3.1 fix (f03d0c4c) added current_user to the library print
  endpoint and plumbed it into the dispatch job object, but the job
  runner never read it back out. _run_print_library_file called
  ArchiveService.archive_print() without created_by_id and never called
  set_current_print_user, so archives created by the printer-card "Print"
  button, File Manager prints, and Library prints all landed with
  created_by_id=NULL and were invisible to the per-user statistics filter.
  The post-print user-targeted notification also had no recipient.

  Forward job.requested_by_user_id to archive_print() at creation time
  and register the current-print user after start_print succeeds,
  matching _run_reprint_archive (lines 686-691).

  Reprint-from-Archive still shows NULL for archives whose original
  created_by_id was NULL — the reprint path reuses the source row as-is
  and only refreshes started_at. Tracked as a separate follow-up.

2026-04-21 13:41:06 +02:00

..

app

fix(dispatch): forward authenticated user through library-print path (#730 follow-up)

2026-04-21 13:41:06 +02:00

tests

feat(printers): show plate name on card for multi-plate active prints (#881)

2026-04-21 09:46:42 +02:00

__init__.py

…