feat: generate persistent task id by wyhash #946
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes several updates and improvements across multiple files in the
dragonfly-client
project. The most important changes include updating dependencies, switching the hashing algorithm, adding logging for better traceability, and modifying request handling to improve error reporting and timeout management.Dependency updates:
Cargo.toml
: Updateddragonfly-api
version from2.1.6
to2.1.9
.dragonfly-client-util/Cargo.toml
: Replacedcrc32fast
withwyhash
version0.5.0
.Hashing algorithm switch:
dragonfly-client-util/src/id_generator/mod.rs
: Switched fromblake3
toWyHash
for file hashing and updated the corresponding test cases. [1] [2] [3]Logging improvements:
dragonfly-client/src/grpc/dfdaemon_download.rs
: Added logging to trace the upload process and task ID generation. [1] [2]dragonfly-client/src/resource/persistent_cache_task.rs
: Added and modified log statements to provide better insight into the cache task process. [1] [2] [3] [4]Request handling improvements:
dragonfly-client/src/grpc/dfdaemon_download.rs
: Added request cloning and timeout setting to improve error reporting and manage request timeouts more effectively. [1] [2]Related Issue
Motivation and Context
Screenshots (if appropriate)