We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Was testing the newly released ValKey client for node, as potential Redis client replacement. It uses NAPI native addon for the core driver.
I'm getting random panics with "Illegal instruction", even though first couple runs and about every other are fine. Simplest repro:
import { GlideClient } from '@valkey/valkey-glide' const client = await GlideClient.createClient({ addresses: [ { host: '127.0.0.1', port: 6379 } ], }) const pong = await client.customCommand(['PING']) console.log(pong) client.close()
No response
Bun v1.1.29 (6d43b36) on linux x86_64 [AutoCommand]
6d43b36
Segmentation fault at address 0x7FCB00000030
ld-temp.o:0
llint_op_call
llint_op_call_ignore_result
Features: jsc, transpiler_cache, tsconfig
The text was updated successfully, but these errors were encountered:
No branches or pull requests
How can we reproduce the crash?
Was testing the newly released ValKey client for node, as potential Redis client replacement. It uses NAPI native addon for the core driver.
I'm getting random panics with "Illegal instruction", even though first couple runs and about every other are fine. Simplest repro:
Relevant log output
No response
Stack Trace (bun.report)
Bun v1.1.29 (
6d43b36
) on linux x86_64 [AutoCommand]Segmentation fault at address 0x7FCB00000030
ld-temp.o:0
:llint_op_call
ld-temp.o:0
:llint_op_call_ignore_result
ld-temp.o:0
:llint_op_call_ignore_result
ld-temp.o:0
:llint_op_call_ignore_result
ld-temp.o:0
:llint_op_call_ignore_result
ld-temp.o:0
:llint_op_call_ignore_result
ld-temp.o:0
:llint_op_call
Features: jsc, transpiler_cache, tsconfig
The text was updated successfully, but these errors were encountered: