You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
thread 'merge_thread_0' panicked at 'assertion failed: `(left == right)`
left: `0`,
right: `1`', /home/trinity/dev/tantivy/bff7c58/src/postings/serializer.rs:203:13
stack backtrace:
0: rust_begin_unwind
at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/panicking.rs:593:5
1: core::panicking::panic_fmt
at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/panicking.rs:67:14
2: core::panicking::assert_failed_inner
3: core::panicking::assert_failed
at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/panicking.rs:229:5
4: tantivy::postings::serializer::FieldSerializer::write_doc
5: tantivy::indexer::merger::IndexMerger::write_postings_for_field
at /home/trinity/dev/tantivy/bff7c58/src/indexer/merger.rs:626:29
6: tantivy::indexer::merger::IndexMerger::write_postings
at /home/trinity/dev/tantivy/bff7c58/src/indexer/merger.rs:658:17
7: tantivy::indexer::merger::IndexMerger::write
at /home/trinity/dev/tantivy/bff7c58/src/indexer/merger.rs:766:9
8: tantivy::indexer::segment_updater::merge
at /home/trinity/dev/tantivy/bff7c58/src/indexer/segment_updater.rs:125:20
9: tantivy::indexer::segment_updater::SegmentUpdater::start_merge::{{closure}}
at /home/trinity/dev/tantivy/bff7c58/src/indexer/segment_updater.rs:518:19
10: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/panic/unwind_safe.rs:271:9
11: std::panicking::try::do_call
at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/panicking.rs:500:40
12: std::panicking::try
at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/panicking.rs:464:19
13: std::panic::catch_unwind
at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/panic.rs:142:14
14: rayon_core::unwind::halt_unwinding
at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/unwind.rs:17:5
15: rayon_core::registry::Registry::catch_unwind
at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/registry.rs:366:27
16: rayon_core::spawn::spawn_job::{{closure}}
at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/spawn/mod.rs:97:13
17: <rayon_core::job::HeapJob<BODY> as rayon_core::job::Job>::execute
at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/job.rs:169:9
18: rayon_core::job::JobRef::execute
at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/job.rs:64:9
19: rayon_core::registry::WorkerThread::execute
at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/registry.rs:859:13
20: rayon_core::registry::WorkerThread::wait_until_cold
at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/registry.rs:793:26
21: rayon_core::registry::WorkerThread::wait_until
at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/registry.rs:768:13
22: rayon_core::registry::WorkerThread::wait_until_out_of_work
at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/registry.rs:817:9
23: rayon_core::registry::main_loop
at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/registry.rs:922:5
24: rayon_core::registry::ThreadBuilder::run
at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/registry.rs:52:18
25: <rayon_core::registry::DefaultSpawn as rayon_core::registry::ThreadSpawn>::spawn::{{closure}}
at /home/trinity/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.12.0/src/registry.rs:97:20
with some printf debugging I found the document causing the crash to be
and more specifically its term payload.comment.created_at:2022-05-01T00:00:01Z, which is actually stored as a d (date == signed integer; you have to flip the 1st bit to decode it): [150, 234, 210, 20, 254, 193, 202, 0]
build with quickwit 163ed7e and tantivy bff7c58497964f947dc94e2e45dfe9962e1d10c3
To reproduce: ingest enough of github archive to trigger a merge, the 1st document of type IssueCommentEvent will cause a panic (or possibly some other kind of document before)
with some printf debugging I found the document causing the crash to be
and more specifically its term
payload.comment.created_at:2022-05-01T00:00:01Z
, which is actually stored as ad
(date == signed integer; you have to flip the 1st bit to decode it):[150, 234, 210, 20, 254, 193, 202, 0]
doc mapper is:
build with quickwit 163ed7e and tantivy bff7c58497964f947dc94e2e45dfe9962e1d10c3
To reproduce: ingest enough of github archive to trigger a merge, the 1st document of type
IssueCommentEvent
will cause a panic (or possibly some other kind of document before)this looks a lot like a variant of quickwit-oss/tantivy#2251, which is supposed to be fixed by quickwit-oss/tantivy#2253
The text was updated successfully, but these errors were encountered: