Skip to content

fix(history): no oversized reconnection warning when deleting a group of raw objects - #452

Merged
PierreRaybaut merged 2 commits into
developfrom
fix/451-group-deletion-reconnection-warning
Oct 28, 2026
Merged

PierreRaybaut merged 2 commits into
developfrom
fix/451-group-deletion-reconnection-warning

Conversation

@PierreRaybaut

Copy link
Copy Markdown
Contributor

Fixes #451.

Problem

Deleting a group of signals or images whose processing results were kept in another group showed an oversized "Delete" warning (OK button only), even when the History panel was not recording: one line per deleted object, labelled with its raw UUID, stating that operations could not be reconnected although there was nothing to reconnect.

Changes

  • find_reconnection_source: only compute actions have a source; UI creation/loading actions report none, whatever their recorded selection.
  • plan_reconnection: report an unreconnected operation only when a recorded processing step loses its source (ReconnectionPlan.warning → unreconnected_operation, holding the operation title).
  • apply_reconnection_plan: apply only when the source is still alive.
  • show_reconnection_warnings: a single message listing each operation once, capped at 10 lines ("... and N more").
  • Docs: History panel guide (EN/FR), 1.4.0 release note (EN/FR), French UI translation.

Tests

  • New regression test: group deletion with and without recording (fails on the previous code: the dialog was shown in both modes).
  • New unit tests: raw/unrecorded objects (no report, no reconnection), message deduplication and cap.
  • History, provenance, deletion and object-view suites: 238 passed.

Deleting a group of signals or images whose results were kept in another
group showed an oversized "Delete" warning, even when the History panel
was not recording: one line per deleted object, labelled with its raw
UUID, although there was nothing to reconnect.

- find_reconnection_source: only compute actions have a source; UI
  creation/loading actions report none, whatever their recorded selection.
- plan_reconnection: report an unreconnected operation only when a
  recorded processing step loses its source (ReconnectionPlan.warning
  becomes unreconnected_operation, holding the operation title).
- apply_reconnection_plan: apply only when the source is still alive.
- show_reconnection_warnings: a single message listing each operation
  once, capped at MAX_LISTED_UNRECONNECTED lines ("... and N more").
- Regression test of group deletion with and without recording, and unit
  tests of raw-object planning and message aggregation.

Closes #451

Assisted-by: Claude Opus 5.5
…anslations)

Describe when the reconnection warning is shown in the History panel
guide, add the 1.4.0 bug-fix note, and update the French translations
(UI message, guide and release notes).

Refs #451

Assisted-by: Claude Opus 5.5
@PierreRaybaut
PierreRaybaut merged commit 14e25aa into develop Oct 28, 2026
6 checks passed
@PierreRaybaut
PierreRaybaut deleted the fix/451-group-deletion-reconnection-warning branch October 29, 2026 05:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant