Skip to content
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.

Sign up for GitHub

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

Jump to bottom

DuckDB integration test: DuckDB error: Binder Error: table positron_b3984 has 2 columns but 1 values were supplied #5308

Closed
testlabauto opened this issue Nov 8, 2024 · 3 comments
Closed

DuckDB integration test: DuckDB error: Binder Error: table positron_b3984 has 2 columns but 1 values were supplied #5308

testlabauto opened this issue Nov 8, 2024 · 3 comments
Assignees
@wesm
Labels
area: duckdb Issues related to positron-duckdb bug Something isn't working

Comments

@testlabauto
Copy link
Contributor

System details:

Positron and OS details:

Ubuntu
Main on 11/08/24

Interpreter details:

N/A

Describe the issue:

https://github.com/posit-dev/positron/actions/runs/11744349205/job/32719239010#step:10:786

Steps to reproduce the issue:

This looks like an intermittent issue with an integration test in CI

Expected or desired behavior:

No integration test failures.

Were there any error messages in the UI, Output panel, or Developer Tools console?

N/A
@wesm wesm self-assigned this Nov 11, 2024
@wesm wesm added bug Something isn't working area: duckdb Issues related to positron-duckdb labels Nov 11, 2024
@wesm wesm mentioned this issue Nov 11, 2024
Merged
@wesm
Copy link
Contributor

wesm commented Nov 11, 2024

I put up an attempted fix in #5328 since I saw this error Error: Catalog Error: Table with name "positron_b3984" already exists! which just suggests an insufficiently random temporary table name

wesm added a commit that referenced this issue Nov 12, 2024
@wesm
Make temp table name in positron-duckdb tests more random to avoid sp…
70e96ec 
…oradic extension test failures (#5328)

Attempts to address #5308 by making temporary table names in the DuckDB
catalog more random. If this does not fix the issue, then I'm not sure
what else it might be, but we can see if the error recurs elsewhere.
@wesm
Copy link
Contributor

wesm commented Nov 12, 2024

I merged the PR -- maybe let's wait a while to see if the error recurs and if so could you please post the new error here?

@testlabauto
Copy link
Contributor Author

Verified Fixed

Positron Version(s) : 2024.12.0-23
OS Version          : OSX

Test scenario(s)

Closing as this has not happened in several runs. Will reopen if it happens again and comment the new error.

Link(s) to TestRail test cases run or created:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wesm wesm

Labels
area: duckdb Issues related to positron-duckdb bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wesm @testlabauto