Chris Roberts

Personally, I worked around this by specifying the response mimetype in the spec as "application/json; UTF-8", e.g. ``` --- snip --- responses: '200': description: OK content: application/json; charset=UTF-8: schema: properties:...

Looking back, I see there was one more element I needed for my workaround: ``` validator = ResponseValidator( spec, custom_media_type_deserializers={"application/json; charset=UTF-8": json.loads}, ) ```

Because logging out doesn't fix this, I'm pretty sure this is an issue related to not clearing all the appropriate cookies that get set upon login when logging out. Simple...

Just managed to pull a logcat when this occurred, but didn't see anything of interest. edit: I can now reliably reproduce this by killing the app's process from Android Studio...

I've heard some reviews complaining about this behavior too. Need to fix for 2.0.

Thank you for you contribution, @wusspuss. I'll be reviewing this sometime this week.

We do capture the exception type, but it's socked away in `$errorCode` ``` % tohil::eval {[][0]} list index out of range % puts $errorCode PYTHON IndexError {list index out of...

tohil initializes the Python interpreter differently than the `python` executable. This results in the contents of `sys.path` being subtly different. A demonstration: ```bash I [nix-shell:~/scratch]$ tclsh

This may be occurring because your database/client's encoding is set to SQL_ASCII (which will prevent the underlying postgres library, psycopg, from decoding strings to Python str objects). Quick example: ```python...

A workaround for the issue was to force the client encoding to utf8 via an environment variable when launching pgcli like so ``` PGCLIENTENCODING=utf8 pgcli ``` This isn't really a...