With the latest Docling 2.97.0 release, DoclingServiceClient convert*() and submit*() methods started to fail for me with the default Docling Serve Docker images (even the latest v1.21.0 with Docling 2.96.1). It took me a couple of hours to understand why. It did not help that the only feedback is Task submission failed. (status=422). Also could not find any information from the Docling Serve container logs, even with debug logs. Hopefully the logs can be improved in the future (docling-project/docling-serve#622).
Bug
Basically, the client now has a Docling version (2.97.0) with the introduction of EMAIL to the InputFormat enum (#3475) while the server (<2.97.0) does not. Then, calling DoclingServiceClient methods without overriding the options from_formats field will default to a list of all client InputFormat values which may not be known by the server.
Steps to reproduce
- Start a Docling Serve instance with
docling<2.97.0.
- In a client with
docling>=2.97.0, call DoclingServiceClient convert*() and submit*() methods.
With the latest Docling 2.97.0 release,
DoclingServiceClientconvert*()andsubmit*()methods started to fail for me with the default Docling Serve Docker images (even the latest v1.21.0 with Docling 2.96.1). It took me a couple of hours to understand why. It did not help that the only feedback isTask submission failed. (status=422). Also could not find any information from the Docling Serve container logs, even with debug logs. Hopefully the logs can be improved in the future (docling-project/docling-serve#622).Bug
Basically, the client now has a Docling version (2.97.0) with the introduction of
EMAILto theInputFormatenum (#3475) while the server (<2.97.0) does not. Then, callingDoclingServiceClientmethods without overriding theoptionsfrom_formatsfield will default to a list of all clientInputFormatvalues which may not be known by the server.Steps to reproduce
docling<2.97.0.docling>=2.97.0, callDoclingServiceClientconvert*()andsubmit*()methods.