Oleg V. Kozlyuk

Greetings. Sorry for delay in getting back to you - can you describe the scenario in which it doesn't work? P.S. Which version are you using?

Hi Thank you for your report, that would be a serious bug. Can you clarify a bit more on how this appeared - was the exception happening somewhere near the...

I have tried to reproduce the issue in a test and it doesn't seem to appear with a synthetic test - a serialization exception is always correctly propagated. Can you...

Please try version 7.5.0 to see if it fixes the issue for you

Sorry - took me a while to get my hands on it. However, for me it works perfectly: ``` Hello, World! O:\Projects\clickhouseclient_bug_replication\ClickHouse.ClientNotSerializing\bin\Debug\net8.0\ClickHouse.ClientNotSerializing.exe (process 21308) exited with code 0. Press any...

For me it is triggered quite perfectly every time  Just to double check, when you say "exception is not thrown", have you checked it in the debugger by putting...

I think there may be just a misunderstanding here, which means I'll need to make docs more clear > When you get the serialization exception that means that no data...

Unfortunately not (closed network, cannot send data) Previous error: `Code: 192. DB::Exception: There is no user "default" in user directories (UNKNOWN_USER)` (error is irrelevant, authentication also fails if `default` user...

Possibly the parameter could be `` - `1` by default, `0` to disable? Then if server returns 401, it can also return following headers (based on whether relevant auth type...

Greetings. Thank you for your contribution. Can you add a test for this exception handling? (e.g. using mocking)