Skip to content

fix: beta feedback batch 2 — metadata, naming, delete confirm, persistence, race condition#1

Open
babo989 wants to merge 5 commits intomainfrom
fix/beta-feedback-batch2
Open

fix: beta feedback batch 2 — metadata, naming, delete confirm, persistence, race condition#1
babo989 wants to merge 5 commits intomainfrom
fix/beta-feedback-batch2

Conversation

@babo989
Copy link
Collaborator

@babo989 babo989 commented Mar 18, 2026

Summary

Five fixes for issues found during beta testing:

  • Metadata IDs (#903, #889-893, #894, #901): Acq_ID and Sample_ID support leading zeros, save confirmation snackbar, metadata info alert
    on acquisition page, flowcell size on magnification labels
  • EcoTaxa naming (#882): Compose fully-qualified project_sample_acq IDs, space-to-underscore sanitization, gallery/explorer URL path
    sanitization
  • Delete confirmation (#904): Confirmation dialog before deleting acquisitions
  • Metadata persistence (#907): Cross-persist lat/lon when setting date/time and vice versa
  • Acquisition race condition: Start acquisition function reads acq_nb_frame and acq_interframe_volume from msg.payload instead of
    relying on globals, preventing stale values when the user changes form fields and immediately clicks Start

babo989 added 5 commits March 18, 2026 21:47
- Acq_ID supports leading zeros (text input + smart increment) (#903)
- Sample_ID as string + save confirmation snackbar (#889-893)
- Show project/sample/operator/gear in acquisition page (#894)
- Add flowcell size (µm) to magnification button labels (#901)
- Compose fully-qualified project_sample_acq IDs in update_config (#882)
- Space-to-underscore sanitization in IDs
- Gallery + Explorer URL path sanitization for legacy TSVs
- Replace direct deleteItem with confirmDelete + dialog
- Show acquisition and sample ID in confirmation prompt
- Warning that deletion cannot be undone
- set object_datetime also persists lat/lon if present
- set object_latlon also persists date/time if present
The start acquisition function read acq_nb_frame and acq_interframe_volume
from Node-RED globals, but the globals were written by a parallel message
path. When the user changed form values and clicked Start, the read happened
before the write, causing the acquisition to use stale values.

Fix: start acquisition now reads from msg.payload first (carried with the
command), falling back to globals for backwards compatibility.

handleAcqStatusChange explicitly passes acq values in the start message.
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