TestLink-API-Python-client icon indicating copy to clipboard operation
TestLink-API-Python-client copied to clipboard

Start of Heading character (␁)

Open KrzysztofSzewczyk opened this issue 1 year ago • 1 comments

when retriving data with SOH character library is crashing

xml.parsers.expat.ExpatError: not well-formed

File "C:\Program Files\Python311\Lib\xmlrpc\client.py", line 1123, in __call__ return self.__send(self.__name, args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Program Files\Python311\Lib\xmlrpc\client.py", line 1465, in __request response = self.__transport.request( ^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Program Files\Python311\Lib\xmlrpc\client.py", line 1167, in request return self.single_request(host, handler, request_body, verbose) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Program Files\Python311\Lib\xmlrpc\client.py", line 1183, in single_request return self.parse_response(resp) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Program Files\Python311\Lib\xmlrpc\client.py", line 1349, in parse_response p.feed(data) File "C:\Program Files\Python311\Lib\xmlrpc\client.py", line 452, in feed self._parser.Parse(data, False) xml.parsers.expat.ExpatError: not well-formed

image

KrzysztofSzewczyk avatar Jan 15 '25 13:01 KrzysztofSzewczyk

Hello @KrzysztofSzewczyk, thanks for your request. It sounds to me like #140 for a TL server issue. Your traceback describes, that server sends not well-formed xml section in its xmlrpc response, maybe wrong encoding breaking? You find in x140 a hint, how to enable a debug to become able to see the internal exchange data.

What I do not understand is the content of your attached picture - describe it a text execution result with a corrupted URL, starting with Xhttp instead http and X is a none ASCII character ?

Regards Luiko

lczub avatar Jan 15 '25 19:01 lczub