[bug]: failed to run custom build command for `tdlib-rs v1.1.0`

[Tony-Rain]

Describe the bug

the project is not being compiled

Reproduction steps

...

Expected behavior

Logs and screenshots

error: failed to run custom build command for tdlib-rs v1.1.0

Caused by:
process didn't exit successfully: /tmp/cargo-installDm2KlS/release/build/tdlib-rs-056355f50fec7c4c/build-script-build (exit status: 101)
--- stdout
cargo:rerun-if-changed=build.rs

--- stderr

thread 'main' panicked at /home/tony/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tdlib-rs-1.1.0/build.rs:167:40:
called Result::unwrap() on an Err value: reqwest::Error { kind: Decode, source: TimedOut }
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: failed to run custom build command for tdlib-rs v1.1.0

Caused by:
process didn't exit successfully: /tmp/cargo-installDm2KlS/release/build/tdlib-rs-056355f50fec7c4c/build-script-build (exit status: 101)
--- stdout
cargo:rerun-if-changed=build.rs

--- stderr

thread 'main' panicked at /home/tony/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tdlib-rs-1.1.0/build.rs:167:40:
called Result::unwrap() on an Err value: reqwest::Error { kind: Decode, source: TimedOut }
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
error: failed to compile tgt v1.0.0, intermediate artifacts can be found at /tmp/cargo-installDm2KlS.
To reuse those artifacts with a future compilation, set the environment variable CARGO_TARGET_DIR to that path.

Method of Installation

Cargo

tgt version

v1.0.0

Operating System (including version and architecture)

Ubuntu 24.04

Terminal and Command Line Interface (CLI) (including versions)

Gnome Terminal

rustc and rustup target (including versions)

rustup 1.28.2 (e4f3ad6f8 2025-04-28)

[FedericoBruzzone]

This error is highly related to: #40 #41 #45

In case you are not able to solve it by following previous issues don't hesitate to expose us the problem.

[kondr1]

$ export RUST_BACKTRACE=1 && cargo build --release --features download-tdlib
   Compiling tdlib-rs v1.1.0
error: failed to run custom build command for `tdlib-rs v1.1.0`
note: To improve backtraces for build dependencies, set the CARGO_PROFILE_RELEASE_BUILD_OVERRIDE_DEBUG=true environment variable to enable debug information generation.

Caused by:
  process didn't exit successfully: `/home/kondr/graveyard/tgt/target/release/build/tdlib-rs-bc294f19217787b2/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=build.rs

  --- stderr

  thread 'main' panicked at /home/kondr/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tdlib-rs-1.1.0/build.rs:167:40:
  called `Result::unwrap()` on an `Err` value: reqwest::Error { kind: Decode, source: TimedOut }
  stack backtrace:
     0: __rustc::rust_begin_unwind
     1: core::panicking::panic_fmt
     2: core::result::unwrap_failed
     3: build_script_build::download_tdlib
     4: build_script_build::main
     5: core::ops::function::FnOnce::call_once
  note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
warning: build failed, waiting for other jobs to finish...
error: failed to run custom build command for `tdlib-rs v1.1.0`
note: To improve backtraces for build dependencies, set the CARGO_PROFILE_RELEASE_BUILD_OVERRIDE_DEBUG=true environment variable to enable debug information generation.

Caused by:
  process didn't exit successfully: `/home/kondr/graveyard/tgt/target/release/build/tdlib-rs-bc294f19217787b2/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=build.rs

  --- stderr

  thread 'main' panicked at /home/kondr/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tdlib-rs-1.1.0/build.rs:167:40:
  called `Result::unwrap()` on an `Err` value: reqwest::Error { kind: Decode, source: TimedOut }
  stack backtrace:
     0: __rustc::rust_begin_unwind
     1: core::panicking::panic_fmt
     2: core::result::unwrap_failed
     3: build_script_build::download_tdlib
     4: build_script_build::main
     5: core::ops::function::FnOnce::call_once
  note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

[FedericoBruzzone]

Hi, thanks for the report.

The issue you’re encountering is caused by a timeout in the build script when attempting to download the TDLib source archive. The download-tdlib feature relies on reqwest internally, and unfortunately, the request is unconditionally .unwrap()ed, so if the download fails (e.g., due to a slow or unstable connection), it will cause a panic during build.

Currently, you cannot increase the timeout or retry count via environment variables or config, this is a limitation of the current implementation.

If your internet connection is stable now, you can simply try running the build again.

[ta3pks]

i have the same bug and this build fails pretty much immediately and i have a pretty stable connection im on fedora 42

[ta3pks]

what if instead of building tdlib from source it links dynamically using system tdlib at least behind a feature flag ?

[FedericoBruzzone]

Hi @ta3pks! I don't understand what you're trying to tell me.

[ta3pks]

im saying is it possible to use tdlib that installed on users system by dynamic linking instead of compiling and static linking as you do @FedericoBruzzone