This is not a permanent fix but a bypass until resolved, rolling back to python 3.11.X resolved the issue. Seems to be compatibility issue between DAP 1.1 and python 3.12.x

this version is riddled with issues

Installed new dap tool on new VM Old VM could run dap syncdb --table accounts no problemsnew dap tool with dap_api_url set to https://api-gateway.instructure.comdap_client_id matching old VM, dap_clie...

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

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

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

This is not a permanent fix but a bypass until resolved, rolling back to python 3.11.X resolved the issue. Seems to be compatibility issue between DAP 1.1 and python 3.12.x

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

Just fyi, if i let the error continue for hours it will load 1.875 million rows into submissions but syncdb will error out saying it was never initiated and to run initdb first and then i will have to...

Hello! sorry for late response.1. Python 3.12.3 (tags/v3.12.3:f6650f9, Apr 9 2024, 14:05:25) [MSC v.1938 64 bit (AMD64)] on win32 2. the old dap tool was working gloriously, had to migrate to new serv...