The root cause of this issue is that the client does not check the response status and try to parse the non-json content returned from the server. Since this status error is not directly shown to users, users only see the json parsing exception.
With this patch, users will see the raw content from the server
It is good to have the visibility but the server parser is still an issue. Any idea on that? From user standpoint, it is hard to correct pdfs as it can be a large volume of docs.
This is related to the issue https://github.com/nlmatics/llmsherpa/issues/64.
The root cause of this issue is that the client does not check the response status and try to parse the non-json content returned from the server. Since this status error is not directly shown to users, users only see the json parsing exception.
With this patch, users will see the raw content from the server
Instead of the implicit one: