make HTTPChunkedStreamBuf::isComplete noexcept#88668
Conversation
|
Workflow [PR], commit [655054a] Summary: ❌
|
|
here we should catch more exceptions. |
Should be renamed, loosing -> losing. |
What kind of exception? Is it possible to make a test? |
Made
Here's the stack trace: |
…stributed_losing_files_after_exception
|
@mstetsyuk, just in case, we have something similar, reproduced in this PR: |
Cherry pick #88668 to 25.8: wrap `~PooledConnection` in try-catch
Cherry pick #88668 to 25.9: wrap `~PooledConnection` in try-catch
| ~PooledConnection() override | ||
| { | ||
| if (bool(response_stream)) | ||
| try |
There was a problem hiding this comment.
I kind of against to do
try {} catch (...) {}
in destructors where it is not necessary.
Here is it is not necessary after you made a proper fix in HTTPChunkedStreamBuf::isComplete.
Backport #88668 to 25.8: wrap `~PooledConnection` in try-catch
Backport #88668 to 25.9: wrap `~PooledConnection` in try-catch
~PooledConnection in try-catchHTTPChunkedStreamBuf::isComplete noexcept
…tion-dtor wrap `~PooledConnection` in try-catch
…tion-dtor wrap `~PooledConnection` in try-catch
25.3.8 Backport of ClickHouse#88668: make `HTTPChunkedStreamBuf::isComplete` noexcept
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):
A
Poco::TimeoutExceptionexception thrown fromPoco::Net::HTTPChunkedStreamBuf::readFromDeviceleads to a crash with SIGABRT.Documentation entry for user-facing changes