ERROR sapient_apex_server.translator.proto_to_proto_translator: translate_v2_to_v1 failed

[dvnicolasdh]

Hello,
Using:

• https://github.com/dstl/Apex-SAPIENT-Middleware/releases/download/v4.2.0/apex-v4.2.0-deploy.zip

Launched first the "start_ellastic.bat" and waited for:

health status changed from [RED] to [GREEN] (reason: [shards started [[.security-7][0]]])." previous.health="RED" reason="shards started [[.security-7][0]]"

Then launched "run_all.bat" and got:

Using a custom socket client built, attempted to send on port 5020 of the SapientMiddleware, the "Default.Registration.json" sapient_message from example ASM1/ of

• https://github.com/dstl/BSI-Flex-335-v2-Test-Harness/releases/download/5.2.4/SAPIENT_Test_Harness_v5.2.4_Executables.zip

correcting the message for snake_case where needed according to "SAPIENT-Proto-Files/bsi_flex_335_v2_0" of

• https://github.com/dstl/SAPIENT-Proto-Files/tree/main/bsi_flex_335_v2_0

We received "REGISTRATION_ACK":

✅ Connected to server
📤 Registration message sent
📥 Server returned a REGISTRATION_ACK message:
acceptance: true

BUT...

On the "Apex GUI", connexion is closed as soon as the message was recevied:

Conection: 0 open (1 closed)

On console of "apex-v4.2.0-deploy\apex.exe" we can see ERROR message:

INFO: Application startup complete.
INFO: Uvicorn running on http://127.0.0.1:8080 (Press CTRL+C to quit)
C:\STAR\APEX-V_TILDE_1.0-D\bin\sapient_apex_server\apex_server.py:130: TrioDeprecationWarning: trio.MultiError is deprecated since Trio 0.22.0; use BaseExceptionGroup (on Python 3.11 and later) or exceptiongroup.BaseExceptionGroup (earlier versions) instead (python-trio/trio#2211)
C:\STAR\APEX-V_TILDE_1.0-D\bin\sapient_apex_server\apex_server.py:187: TrioDeprecationWarning: MultiError.catch is deprecated since Trio 0.22.0; use except* or exceptiongroup.catch() instead (python-trio/trio#2211)
2026-05-05 07:40:53,992 INFO apex: Connection inserted (id: 1, socket: 172.18.5.253:45418)
2026-05-05 07:40:54,002 ERROR sapient_apex_server.translator.proto_to_proto_translator: translate_v2_to_v1 failed, got error: Failed to parse mode_definition field: Failed to parse detection_class_definition field: Message type "sapient_msg.bsi_flex_335_v1_0.Registration.DetectionClassDefinition" has no field named "taxonomy_dock_definition" at "SapientMessage.registration.mode_definition[0].detection_definition.detection_class_definition[0]".
Available Fields(except extensions): "['confidenceDefinition', 'classPerformance', 'classDefinition']"..
2026-05-05 07:40:54,010 INFO apex: Connection 1 fatal error: Connection closed
2026-05-05 07:40:54,013 INFO apex: Connection disconnection update (id: 1)

replaced ~ with TILDE for readability

Seems that apex.exe attempts but fails to translate_v2_to_v1 as it doesn't recognize "taxonomy_dock_definition" field. Although the field is present in the Harness example and seems to be defined for v2 according to:

• https://github.com/dstl/SAPIENT-Proto-Files/blob/main/bsi_flex_335_v2_0/registration.proto#L215

May apex conversion need adjustments ?

[dvnicolasdh]

Added sending status_report every 5 seconds and removed :

                            ,
                          "taxonomy_dock_definition": [
                               {
                                   "Dock_class_namespace": "sapient_core",
                                   "Dock_class": "Land Vehicle.2 Wheels.Other",
                                   "Extension_subclass": [
                                       {
                                           "Subclass_namespace": "https://auto.schema.org/",
                                           "Subclass_name": "MotorizedBicycle",
                                           "units": "probability"
                                       }
                                   ]
                               }
                           ]

from the sapient_message with registration and attempted sending to apex, and also got:

✅ Connected to server
📤 Registration message sent
📥 Server returned a REGISTRATION_ACK message:
acceptance: true

But connection still closes on "Apex GUI"

connection still closes

And error on the apex.exe console:

2026-05-05 09:29:19,368 ERROR sapient_apex_server.translator.proto_to_proto_translator: translate_v2_to_v1 failed, got error: Failed to parse mode_definition field: Failed to parse task field: Failed to parse command field: Invalid enum value COMMAND_TYPE_PATROL for enum type sapient_msg.bsi_flex_335_v1_0.Registration.CommandType at SapientMessage.registration.mode_definition[0].task[0].command[0].type...

COMMAND_TYPE_PATROL exists in v2, but not in v1.
Conversion might not be possible, if so, apex may not receive some v2 messages?

[dvnicolasdh]

changed command_type to COMMAND_TYPE_LOOK_AT
as COMMAND_TYPE_MOVE_TO, COMMAND_TYPE_PATROL and COMMAND_TYPE_FOLLOW are not part of v1...

1. not all v2 command type can be migrated to v1....

Then connection attempt seems OK, Apex GUI shows:

Apex.exe console do not show errors:

INFO: Application startup complete.
INFO: Uvicorn running on http://127.0.0.1:8080 (Press CTRL+C to quit)
C:\STAR\APEX-V_TIDLE_1.0-D\bin\sapient_apex_server\apex_server.py:130: TrioDeprecationWarning: trio.MultiError is deprecated since Trio 0.22.0; use BaseExceptionGroup (on Python 3.11 and later) or exceptiongroup.BaseExceptionGroup (earlier versions) instead (python-trio/trio#2211)
2026-05-05 10:05:39,333 INFO apex: Connection inserted (id: 1, socket: 172.18.5.253:55260)
C:\STAR\APEX-V_TIDLE_1.0-D\bin\sapient_apex_server\apex_server.py:187: TrioDeprecationWarning: MultiError.catch is deprecated since Trio 0.22.0; use except* or exceptiongroup.catch() instead (python-trio/trio#2211)

Note: replace TIDLE with ~

2. But.. attempting to open REST API gives:

503 Error: Service Unavailable

Note, ran "install_elastic.bat" in the same folder where it is, hence the script installed "elasticsearch-8.11.1" as a subfolder where it was ran.
Hence corrected the "elasticConfig.certLocation" to point where the actual http_ca.crt were deployed. But this did not change the 503 Error: Service Unavailable.