-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
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
Serveral internal errors found in nightly build #12009
Comments
Thanks for finding these bugs and reporting this issue! Just curious, do you find these through normal duckdb usage or are these the result of some sort of automatic testing/fuzzing? |
Hello! They are discovered by my in-developing DBMS testing framework. |
Make sure the quantile number list is not itself NULL. fixes: duckdblabs/duckdb-internal#2021
Issue #12009: APPROX_QUANTILE NULL List
What happens?
I found several internal errors in the nightly build.
Maybe they are not bugs or flaws. I just list them here.
To Reproduce
All PoCs except PoC No.6 can be reproduced on both the release cli binary v0.10.2 (
duckdb_cli-linux-amd64
) and the nightly build in python.PoC No.1:
PoC No.2:
PoC No.3, maybe related to issue #12004 :
PoC No.4:
PoC No.5:
PoC No.6:
PoC No.7:
PoC No.8:
PoC No.9, maybe related to issue #12008 :
PoC No.10:
PoC No.11:
Note that PoC No.6 can only be reproduced on the nightly build in python with the following code:
Output:
Other PoCs can be reproduced on both the release cli binary v0.10.2 and the nightly build in python.
OS:
Ubuntu 22.04 x64
DuckDB Version:
v0.10.2 or nightly build (v0.10.3-dev848)
DuckDB Client:
cli (0.10.2) or Python (nightly build)
Full Name:
Jingzhou Fu
Affiliation:
Wingtecher Lab of Tsinghua University
What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.
I have tested with a nightly build
Did you include all relevant data sets for reproducing the issue?
Yes
Did you include all code required to reproduce the issue?
Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?
The text was updated successfully, but these errors were encountered: