-
Type:
Task
-
Status: Done (View Workflow)
-
Priority:
Normal
-
Resolution: Done
-
Component/s: ics_mcsActor
-
Labels:None
Somehow the `np` type is leaking through into psycopg2 innards. Is this from the Rubin 10 update? Why have we not seen it in the last week?
2025-11-11 05:58:52.787Z mcscmd 20 McsCmd.py:1076 Writing transformation coefficients to DB.
2025-11-11 05:58:52.803Z cmds 20 CommandLink.py:122 > 2 5 w text="Failed to do fibreID: (psycopg2.errors.InvalidSchemaName) schema "np" does not exist
LINE 1: ...s_boresight_y_pix, calculated_at) VALUES (132988, np.float64...
^
[SQL: INSERT INTO mcs_boresight (pfs_visit_id, mcs_boresight_x_pix, mcs_boresight_y_pix, calculated_at) VALUES (%(pfs_visit_id)s, %(mcs_boresight_x_pix)s, %(mcs_boresight_y_pix)s, %(calculated_at)s)]
[parameters: {'pfs_visit_id': 132988, 'mcs_boresight_x_pix': np.float64(4439.91726622), 'mcs_boresight_y_pix': np.float64(2838.91397636), 'calculated_at': 'now'}]
(Background on this error at: https://sqlalche.me/e/20/f405)"
- relates to
-
-
- Won't Fix
-