lance-format/lance

lance run benchmark panic

Open

#2,491 opened on Jun 19, 2024

View on GitHub
 (2 comments) (1 reaction) (0 assignees)Rust (695 forks)github user discovery
benchmarkbuggood first issuehelp wantedrust

Repository metrics

Stars
 (6,582 stars)
PR merge metrics
 (Avg merge 6d 1h) (219 merged PRs in 30d)

Description

steps to reproduce: 1: git clone lance(44d978be5b4e483597f3422affd7999c68) 2: run RUST_BACKTRACE=1 cargo bench -- bench_hnsw

panic output:

Contributor guide

Research direction
Investigate the panic in the HNSW benchmark by running with RUST BACKTRACE=1 and examining the code path for HNSW index construction or search. Look for potential null pointer dereferences, out of bounds access, or assertion failures.
Tech stack
rust
Domain
backenddatabase
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
RustCargo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70