Crate batch_mode_process_response

Constants§

DEFAULT_OUTPUT_FILE_BRIDGE: The const pointer the macro references.
PROCESS_ERROR_FILE_BRIDGE: We expose a CONST of type BatchWorkflowProcessErrorFileFn, so passing &PROCESS_ERROR_FILE_BRIDGE exactly matches the trait’s needed function pointer type.

default_output_file_bridge_fn: A default bridging function, if the user doesn’t specify a particular T type. We’ll parse each line as a CamelCaseTokenWithComment or whichever default type we prefer.
deserialize_json_with_optional_fields_wrapper: Attempt to deserialize json_value into T.
If the top‐level attempt fails, the function looks for a nested "fields" object and tries again.
All paths are heavily traced so we can see exactly where deserialization succeeds or fails.
handle_failed_json_repair
handle_finish_reason_length
handle_successful_response
process_batch_output_and_errors: We add 'static + Send + Sync to T, so that storing it in an Arc<dyn ... + Send + Sync + 'static> is valid and the resulting Future can be Send.
process_error_data
process_error_file: This is the real async function that processes the error file for a given triple,using the list of error operations. Now uses NDJSON approach line by line.
process_output_data
process_output_file: The core async function to process the output file for a given triple.Now we do NDJSON line-by-line parsing, just like the older batch-mode approach.
process_output_file_bridge_fn: The bridging function EXACTLY matches the BatchWorkflowProcessOutputFileFn type:
save_failed_entries