We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This morning, the fuzzer triggered another assertion error:
SELECT upper(decode('\xF6\x96\xB0\x85'::BLOB)::VARCHAR);
src/function/scalar/string/caseconvert.cpp:64: duckdb::idx_t duckdb::GetResultLength(const char *, duckdb::idx_t) [IS_UPPER = true]: Assertion `new_sz >= 0' failed.
After some digging, I see Utf8Proc::Analyze is missing validation for Unicode characters not representable by UTF8 as described here: https://en.wikipedia.org/wiki/UTF-8#cite_note-16
This is an issue from my side as well because I shouldn't generate these strings either :) I am going to add the missing validation.
Run the query above.
Linux
latest from sources
Shell
Pedro Ferreira
Huawei
master
The text was updated successfully, but these errors were encountered:
Fix for issue duckdb#4708
740c52f
Merge pull request #4711 from PedroTadim/fix4708
a991bea
Fix for issue #4708
Fixed by #4711
Sorry, something went wrong.
No branches or pull requests
What happens?
This morning, the fuzzer triggered another assertion error:
src/function/scalar/string/caseconvert.cpp:64: duckdb::idx_t duckdb::GetResultLength(const char *, duckdb::idx_t) [IS_UPPER = true]: Assertion `new_sz >= 0' failed.
After some digging, I see Utf8Proc::Analyze is missing validation for Unicode characters not representable by UTF8 as described here: https://en.wikipedia.org/wiki/UTF-8#cite_note-16
This is an issue from my side as well because I shouldn't generate these strings either :) I am going to add the missing validation.
To Reproduce
Run the query above.
OS:
Linux
DuckDB Version:
latest from sources
DuckDB Client:
Shell
Full Name:
Pedro Ferreira
Affiliation:
Huawei
Have you tried this on the latest
master
branch?Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?
The text was updated successfully, but these errors were encountered: