proseg
proseg copied to clipboard
parquet reading error
I have this error when running proseg 2.0.0 on one of my xenium samples, while others run fine:
Using 16 threads
thread 'main' panicked at src/sampler/transcripts.rs:448:10:
called `Result::unwrap()` on an `Err` value: General("Invalid Parquet file. Corrupt footer")
stack backtrace:
0: 0x55cf9f02962a - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::ha4a311b32f6b4ad8
1: 0x55cf9f04e923 - core::fmt::write::h1866771663f62b81
2: 0x55cf9f026a53 - std::io::Write::write_fmt::hb549e7444823135e
3: 0x55cf9f029472 - std::sys::backtrace::BacktraceLock::print::hddd3a9918ce29aa7
4: 0x55cf9f02a57c - std::panicking::default_hook::{{closure}}::h791f75256b902d7d
5: 0x55cf9f02a3c2 - std::panicking::default_hook::h82cc572fcb0d8cd7
6: 0x55cf9f02ab57 - std::panicking::rust_panic_with_hook::he21644cc2707f2c4
7: 0x55cf9f02a9ea - std::panicking::begin_panic_handler::{{closure}}::h42f7c414fed3cad9
8: 0x55cf9f029b09 - std::sys::backtrace::__rust_end_short_backtrace::ha26cf5766b4e8c65
9: 0x55cf9f02a67c - rust_begin_unwind
10: 0x55cf9e6e0000 - core::panicking::panic_fmt::h74866b78e934b1c0
11: 0x55cf9e6e03e6 - core::result::unwrap_failed::h899ed7ab2ccb8159
12: 0x55cf9e7c74a9 - proseg::sampler::transcripts::read_xenium_transcripts_parquet::h9701ee74cab56332
13: 0x55cf9e7be8df - proseg::sampler::transcripts::read_transcripts_csv::hb1c74b99959c70a7
14: 0x55cf9e80eedc - proseg::main::h05179402303c55ee
15: 0x55cf9e7ff023 - std::sys::backtrace::__rust_begin_short_backtrace::hc425dc0589a4b2c2
16: 0x55cf9e7c9fb9 - std::rt::lang_start::{{closure}}::h8be2d181d7192c45
17: 0x55cf9f01f5f7 - std::rt::lang_start_internal::h78dd36c15a6b42b8
18: 0x55cf9e834935 - main
19: 0x7fd4452991ca - <unknown>
20: 0x7fd44529928b - __libc_start_main
21: 0x55cf9e6e0645 - _start
22: 0x0 - <unknown>
They were generated by these versions:
"instrument_sw_version": "3.1.0.0",
"analysis_sw_version": "xenium-3.1.0.4",
And I was able to read the parquet file fine from python using pandas.read_parquet or from rust 1.84.0
Huh, not sure what might cause this. If you're able, can you try proseg 3 and see if you get the same error?