recovery_worker.hpp

1. Overview

The recovery_worker.hpp file runs selected recovery operations outside the GTK main thread and reports completion.

This is an interface and data-contract file. It declares the public and internal types used by this subsystem, allowing implementation files and callers to share a stable compile-time contract.

Its paired source or interface file is recovery_worker.cpp.

Primary responsibilities:

  • Accept source, destination and selected results
  • Execute recovery asynchronously
  • Marshal completion back to the UI
  • Support worker lifecycle control

2. File Identity and Scope

  • Source path: src/recovery_worker.hpp
  • Language: C++
  • File role: interface and data-contract file
  • Physical lines: 38
  • Non-empty lines: 31
  • SHA-256: 494960f3c195b7f0a65a73ba7f2e57dd95fff62cdc6227991a034aa731b0ce78

The declarations in this file use the global namespace.

3. Dependencies

3.1 Project Headers

  • models.hpp
  • recovery_exporter.hpp

3.2 Standard and External Headers

  • atomic
  • functional
  • string
  • thread
  • vector

These dependencies define the file’s compile-time integration with the recovery engine, GTK interface, on-disk format decoders, operating-system services, or C++ standard library.

4. Declared Types

  • struct RecoveryResult.
  • class RecoveryWorker.

5. Constants and Configuration Values

No preprocessor or compile-time constants were detected as top-level declarations in this file.

6. Data Members and Persistent State

The interface declares the following state-bearing members:

  • bool ok {false}
  • RecoverySummary summary
  • std::vector<std::string> logs
  • std::string error
  • std::atomic<bool> cancel_requested_{false}
  • std::atomic<bool> running_ {false}
  • std::thread thread_

These members hold configuration, parser context, UI widgets, source references, progress state, recovered metadata, or temporary resources according to the owning type.

7. API and Function Inventory

The following callable interfaces or definitions were detected:

  • ~RecoveryWorker() – Destroys the object and releases resources owned by the instance.
  • void start(const ScanReport&report,const std::string&output_dir,const std::vector<size_t>&selected_result_indices,CompletionCallback cb) – Implements the operation identified by this API and updates or returns the associated state.
  • bool running()const – Implements the operation identified by this API and updates or returns the associated state.
  • void join() – Implements the operation identified by this API and updates or returns the associated state.
  • void request_cancel() – Implements the operation identified by this API and updates or returns the associated state.

8. Operational Flow

The subsystem represented by this file normally participates in the following flow:

  1. Accept source, destination and selected results.
  2. Execute recovery asynchronously.
  3. Marshal completion back to the UI.
  4. Support worker lifecycle control.
  5. Expose or execute the detected APIs: ~RecoveryWorker, start, running, join, request_cancel.
  6. Return explicit results, progress data, recovered records, or diagnostics to the calling layer.

9. Validation and Error Handling

  • Errors are propagated through Boolean results, error strings, logs, exceptions, or status records depending on the API.
  • Byte offsets, sizes and lengths must be validated before arithmetic and before every read to avoid overflow and out-of-bounds access.

10. Runtime, Concurrency, and Resource Management

  • Concurrency: the file contains worker-thread or synchronization primitives; UI updates and shared state must remain thread-safe.

11. Security and Data-Recovery Considerations

  • Recovery code should prefer read-only source access and avoid writing to the original damaged medium.
  • Raw devices and image files are treated as untrusted binary input; every offset and length must remain bounded by the source size.
  • Recovered names and destination paths must be sanitized to prevent directory traversal and accidental overwrite outside the selected export directory.

12. Implementation Considerations

  • Changes to public declarations can affect every translation unit that includes this header and should preserve binary and source compatibility where required.
  • State-bearing members should have explicit ownership and initialization semantics, especially for references, pointers, file descriptors and GTK widgets.

13. Integration with the Recovery Pipeline

  • The file belongs to the orchestration layer between the UI and low-level parsers.
  • It aggregates progress, results and diagnostics from multiple modules.
  • It should preserve cancellation and completion semantics across thread boundaries.

14. Licensing and Provenance

No explicit copyright or software-license statement was detected in the opening section of this individual file. Distribution terms should therefore be verified against the project-level license and repository metadata.

The SHA-256 value in this document can be used to associate the generated documentation with the exact source version analyzed.

Published on:
Last updated on: