bug_report.yml
bug_report.yml
| Name | About | Labels | Assignees |
|---|---|---|---|
| Bug report | Create a report to help us improve | needs triage |
DuckDB has several repositories for different components, please make sure you're raising your issue in the correct one:
- Documentation
- Clients: Go, Java (JDBC), Node.js, ODBC, Python, R, Rust, WebAssembly (Wasm)
- Extensions:
aws,azure,delta,ducklake,encodings,excel,fts,httpfs,iceberg,inet,lance,mysql,postgres,spatial,sqlite,ui,unity_catalog,vortex,vss
If the issue occurs in core DuckDB (e.g., a SQL query crashes or returns incorrect results) or if the issue is in the DuckDB command line client, feel free to raise it in this repository.
Please report security vulnerabilities using GitHub's report vulnerability form.
A short, clear and concise description of what the bug is.
Please provide steps to reproduce the behavior, preferably a minimal reproducible example. Please adhere the following guidelines:
-
Format the code and the output as code blocks using triple backticks:
``` CODE HERE ``` -
Add all required imports for scripts, e.g.,
import duckdb,import pandas as pd. -
Remove all prompts from the scripts. This include DuckDB's 'D' prompt and Python's
>>>prompt. Removing these prompts makes reproduction attempts quicker. -
Make sure that the script and its outputs are provided in separate code blocks.
-
If applicable, please check whether the issue is reproducible via running plain SQL queries from the DuckDB CLI client.
Environment (please complete the following information):
Please include operating system version and architecture (e.g., aarch64, x86_64, etc.).
Identity Disclosure:
If the above is not given and is not obvious from your GitHub profile page, we might close your issue without further review. Please refer to the reasoning behind this rule if you have questions.