We found a couple of bugs in the opal-python-client that prevented us from running our data integration pipeline with opal.
We are using Opal 4.2.6 and opal-python-client 4.1.1.
First, the "import-csv" command was always returning a status of "2"; turned out that the code was checking for the response header "Location" instead of "location".
Second, the "dict" command was sometimes returning in error; turned out some of our variables had descriptions with accented characters, and sometimes a chunk of data would get just the first byte of a UTF-8 character. We did a fix that converts the bytearray buffer into a string just at the very end of the receive.
I include the patched python files (io.py + core.py) in this post.
Could you please check these files and incorporate the fixes into release 4.1.2?