Skip to content

rustic-rs Crash Report #1877

Description

@Insomniac66

Was playing around with rustic a bit and comparing it to restic when I encountered a crash during a prune --forget operation. (I believe while fetching the index, but I am not certain. There was no cache present on the system at the start of the command.)

Report:

name = "rustic-rs"
operating_system = "Linux (NixOS 26.11) [x86_64]"
crate_version = "0.11.3"
explanation = """
Panic occurred in file '/build/rustic-0.11.3-vendor/source-registry-0/rustic_core-0.12.0/src/blob/tree.rs' at line 683
"""
cause = 'called `Result::unwrap()` on an `Err` value: "SendError(..)"'
method = "Panic"
backtrace = """
   0:     0x5f4012d4b5b7 - human_panic[8a8d38a999ebdf65]::panic::setup_panic::<<rustic_rs[814f049e9eb3bf83]::commands::EntryPoint as abscissa_core[c5ea2ab1b3261721]::runnable::Runnable>::run::{closure#2}>::{closure#0}
   1:     0x5f4012e0a2d0 - std[5d98751fec7814e2]::panicking::panic_with_hook
   2:     0x5f4012e242c1 - std[5d98751fec7814e2]::panicking::panic_handler::{closure#0}
   3:     0x5f4012e24279 - std[5d98751fec7814e2]::sys::backtrace::__rust_end_short_backtrace::<std[5d98751fec7814e2]::panicking::panic_handler::{closure#0}, !>
   4:     0x5f4012e07d2c - __rustc[e5c730d067dcbd95]::rust_begin_unwind
   5:     0x5f4011bf220b - core[4a460fc38180a4ea]::panicking::panic_fmt
   6:     0x5f4011bf2311 - core[4a460fc38180a4ea]::result::unwrap_failed
   7:     0x5f40129a0519 - std[5d98751fec7814e2]::sys::backtrace::__rust_begin_short_backtrace::<<rustic_core[d9d2e3df5b76dd23]::blob::tree::TreeStreamerOnce>::new<rustic_core[d9d2e3df5b76dd23]::backend::decrypt::DecryptBackend<rustic_core[d9d2e3df5b76dd23]::crypto::aespoly1305::Key>, rustic_core[d9d2e3df5b76dd23]::index::GlobalIndex>::{closure#0}, ()>
   8:     0x5f4012c01f0b - <std[5d98751fec7814e2]::thread::lifecycle::spawn_unchecked<<rustic_core[d9d2e3df5b76dd23]::blob::tree::TreeStreamerOnce>::new<rustic_core[d9d2e3df5b76dd23]::backend::decrypt::DecryptBackend<rustic_core[d9d2e3df5b76dd23]::crypto::aespoly1305::Key>, rustic_core[d9d2e3df5b76dd23]::index::GlobalIndex>::{closure#0}, ()>::{closure#1} as core[4a460fc38180a4ea]::ops::function::FnOnce<()>>::call_once::{shim:vtable#0}
   9:     0x5f4012e24f0f - <std[5d98751fec7814e2]::sys::thread::unix::Thread>::new::thread_start
  10:     0x7a8f10804e53 - start_thread
  11:     0x7a8f1088c07c - __clone3
  12:                0x0 - <unresolved>
"""

Command:

rustic forget \
    --use-profile docker-services.toml \
    --prune \
    --keep-pack 90d \
    --keep-last 5 \
    --keep-hourly 72 \
    --keep-daily 31 \
    --keep-monthly 12 \
    --keep-yearly 10

Profile (redacted):

[repository]
repository = "opendal:s3"
password = "..."

[repository.options]
access_key_id = "..."
secret_access_key = "..."
endpoint = "https://s3.eu-central-2.wasabisys.com"
region = "eu-central-2"
bucket = "..."
root = "docker-services"

Outside of this I've been having a pretty good experience however, I am impressed by how well rustic handled a decent size repo with > 100k snapshots.

Metadata

Metadata

Assignees

No one assigned

    Labels

    S-triageStatus: Waiting for a maintainer to triage this issue/PR

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions