@StevenWalls  Thank you for the details. With the information you provided, I have been able to reproduce the error you experienced. So far, I got to the conclusion that this error ("Fatal Pyt...

@michael60 Actually, on the Windows side, the DAP library gets tested on Windows Server 2022 before release, which has the same kernel and core components as Windows 11, so we list Windows 11 as s...

@StevenWalls that is a strange error. I'd really like to reproduce this somehow in my development environment. Can you tell us what version of Python and PostgreSQL and Windows are you using? ...

@StevenWalls You wrote Our issue now is, none of our newly created tables can be synced. Since the dap update when we create a table it is not being added to the new table_sync table, so when we ...

@StevenWalls, Thanks for bringing up the temp folder issue. Since v1.0.0, we've updated how temporary folders are handled, and so far, haven't encountered any problems with cleanup. Howeve...

@michael60 Thank you, I checked your console output, I would've expected some kind of error message that could help but unfortunately there is none. What you could try is upgrading the `ts...

@michael60 I'm thinking there might be more detailed log coming to the console when running the client, compared to what gets logged to the log file. The "Fatal Python error" that I me...

@lmsstaff The behavior you explained was present already in v1.0.0 too, there was no change in v1.1.0 affecting namespaces. And it is the expected behavior; the --namespace argument is not optiona...

@michael60 This error (`ERROR - module 'socket' has no attribute 'TCP_KEEPIDLE'`) is already known to us, it'll be fixed in the next release of the client library, comi...

@michael60 Actually, on the Windows side, the DAP library gets tested on Windows Server 2022 before release, which has the same kernel and core components as Windows 11, so we list Windows 11 as s...