-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
"Storage is about to be deleted. Core dumped" exception when running chdb-node
.
#11
Comments
I confirm I'm not unintentionally calling |
We also noticed that this is always happening after performing 4 or 5 queries (no less, no more). |
The following script triggers the error in my CI env:
And below are the CI container info:
|
Note that I also tried to use the latest version of chdb (1.4.1) and got the same error. |
chdb-node
.chdb-node
.
Can not reproduce it on my macOS + node v16. Testing on Linux |
Reproduced on Linux + Node 20 |
PR: chdb-io/chdb#227 |
Fixed #12 |
Hi there,
We have a ClickHouse Cloud service in production and we're trying to use
chdb-node
in our tests suite to simulate that service.When running our tests suite we run into an issue where an exception is raised from the ClickHouse engine and we're having a hard time identifying what's wrong.
For each series of tests, we instantiate a new Session, perform some operations and then clean up the session.
After a few operations, we get the following error:
We also get the following one (but less often):
Configuration:
I'm curious if you guys ran into this issue in other context.
I also wrote a simple script that generates many sessions in series and for each session performs a few
insert
andselect
operations, and I didn't encounter the problem. So it could be something with our CI suite but so far I'm clueless.I'm pretty positive I'm not deleting the session while it's been used but maybe I made a mistake.
Any pointers or ideas would be much appreciated. Also happy to re-post this somewhere else if it's more suitable there.
Thank you.
The text was updated successfully, but these errors were encountered: