Issues

• incorrect behavior and out of bounds accesses with keys that are prefixes of other keys

  armon/libart#56 · Filter by author mux opened on Oct 25, 2025

• search get null when str2 = str1 + '\0'

  armon/libart#54 · Filter by author zhou317 opened on Jan 4, 2024

• Is it thread safe?

  armon/libart#53 · Filter by author KeeProMise opened on Jun 28, 2022
  7

• bugs for art_insert in some case

  armon/libart#51 · Filter by author yizhang2077 opened on Feb 12, 2022
  1

• If libart support longest prefix match ?

  armon/libart#50 · Filter by author hi-glenn opened on Jan 23, 2022

• Integer keys need byte-ordering swap?

  armon/libart#49 · Filter by author pohchaichon opened on Nov 27, 2021
  1

• please review SSE instructions

  armon/libart#47 · Filter by author svalaskevicius opened on Mar 26, 2021
  2

• Tag pointers to avoid node type byte

  armon/libart#46 · Filter by author adamsch1 opened on Dec 31, 2020
  1

• Range scan performance

  armon/libart#43 · Filter by author JohannesLichtenberger opened on Mar 12, 2020

• [BUG] key_len not work with longer key

  armon/libart#42 · Filter by author pengtianabc opened on Jan 4, 2020

• art_iter_prefix depth goes over key_len

  armon/libart#40 · Filter by author lmcmgig opened on Feb 5, 2019

• Possible to do range scans with ART ?

  armon/libart#38 · Filter by author winash12 opened on Sep 26, 2018

• Crash in recursive_insert

  armon/libart#35 · Filter by author romanbsd opened on Apr 8, 2018

• art_insert() should return a return code

  armon/libart#19 · Filter by author kellabyte opened on Dec 22, 2015
  5

• Adding a key which is a full prefix of another leads to valgrind warning

  armon/libart#17 · Filter by author nmav opened on Oct 21, 2015
  1

• Check return codes everywhere

  armon/libart#16 · Filter by author elfring opened on Oct 6, 2015

• avoid storing full keys in leafs

  armon/libart#10 · Filter by author wastl opened on Jun 6, 2014
  3