Error running initdb with DAP 1.1

[StevenWalls]

On several table downloads using initdb I'm getting dozens of the error below. This has only been on a few tables so far. I have tried dropping the table and re-running, that worked once but not on the conversation_messages table.  We're using Python 3.12, DAP 1.1, Postgresql 15.6

File "C:\Program Files\Python312\Lib\asyncio\selector_events.py", line 1133, in _write_send
assert self._buffer, 'Data should not be empty'
AssertionError: Data should not be empty

[RichardCarballo]

My error matched exactly except in line 1137 
in case you do not get a reply, I am working with an Team member at the following post:
CD2-dap-issues

[StevenWalls]

@RichardCarballo  Thanks. I never heard anything so I opened a ticket with Instructure support. It was escalated but I haven't heard back yet.

[RichardCarballo]

I was able to resolve my issue by uninstalling python 3.12 and installing python 3.11, hope this works for you!

[StevenWalls]

Wow... and we recently upgraded to 3.12 because 3.9 didn't work..

[kdoherty2]

HI @StevenWalls @RichardCarballo   Did you ever get a resolution to this issue?  We are running Python 3.12, DAP 1.4 and Postgres 16.

We get the same error you previously reported:  AssertionError: Data should not be empty

Thanks for any help you can provide.

[kdoherty2]

It appears that our issue is addressed in the post below under "

assert self._buffer, 'Data should not be empty'.

https://community.canvaslms.com/t5/The-Product-Blog/DAP-CLI-amp-Lib-1-3-0-Release-Microsoft-SQL-Supp...