You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(dc_bridge): carry Measurement custom keys onto File metadata Records
A Measurement's `custom_key_str_list` keys reached its Records but not the
Uploader's `file_status`/`group_complete` rows, which were built from a fixed
field set — so the Records and the Files of one Measurement ended up labelled
differently, with nothing logged.
A Record now names its custom keys in a `custom_keys` field, which is the only
way the Uploader can tell `site` from a measured field. Those keys are appended
to every File metadata row, including retention's shed rows.
Dropped rather than written, in both cases from every row kind so a File and its
group marker can't disagree:
- a key naming a field the Uploader computes itself (`storage_type`, `size`, …)
— the Uploader's value is kept and the Bridge warns;
- `name`, `id` and `robot_name`, which the rows already carry as `group_name`,
`robot_id` and `robot_name` — re-emitting `id` would put a robot identifier in
whatever an `id` column happens to be.
A Measurement with no custom keys produces the rows it did before.
Closes#419
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015oGKFjBD4WKxMHYv3iKXBo
Signed-off-by: David Bensoussan <d.bensoussan@proton.me>
0 commit comments