Skip to content

Crash bug when log() is used in order by clause (SQLancer) #11549

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
2010YOUY01 opened this issue Jul 19, 2024 · 0 comments · Fixed by #11571
Closed

Crash bug when log() is used in order by clause (SQLancer) #11549

2010YOUY01 opened this issue Jul 19, 2024 · 0 comments · Fixed by #11571
Assignees
Labels
bug Something isn't working

Comments

@2010YOUY01
Copy link
Contributor

Describe the bug

Reproducer in datafusion-cli

DataFusion CLI v40.0.0
> create table t3(v1 int);

0 row(s) fetched.
Elapsed 0.065 seconds.

> select * from t3 order by log(v1);
thread 'main' panicked at /Users/yongting/Desktop/code/my_datafusion/arrow-datafusion/datafusion/functions/src/math/log.rs:85:42:
index out of bounds: the len is 1 but the index is 1
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

It is likely this bug is only related to log function implementation. Perhaps it could be a good first issue.

To Reproduce

No response

Expected behavior

No response

Additional context

Found by SQLancer #11030

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants