gitbutlerapp/gitbutler
1
1
Fork 0
mirror of https://github.com/gitbutlerapp/gitbutler.git synced 2024-12-18 14:31:30 +03:00
Code Issues Packages Projects Releases Wiki Activity
44c64565a2
gitbutler/crates/gitbutler-watcher/Cargo.toml

41 lines
779 B
TOML
Raw Normal View History

add `watcher` crate with code copied from `gitbutler-tauri/src/watcher`. It's not functional yet, but exactly at the spot where it needs fixing across the boundary that is: - a stand-in for application events - analytics
2024-04-17 20:11:24 +03:00
[package]
name = "gitbutler-watcher"
version = "0.0.0"
edition = "2021"
publish = false
on Windows, update far less often on filesystem changes. (#3601) By increasing the window size for collecting filesystem events, knowing that each event is processed in parallel, we might be lucky and that already reduces the likelyhood of clashes. It's an experiment though. On Unix, run with: `LOG_LEVEL=debug pnpm tauri dev --features adapt-to-windows`
2024-04-25 08:16:41 +03:00
[features]
default = []
## A trial to see if doing things differently on Windows helps with #3601
address review comments - rename feature to `windows` - remove unused config key from `Cargo.toml`, unfortunately `cfg` isn't available for everything - make sure feature is toggled on on CI when checking and when publishing
2024-04-25 12:17:52 +03:00
windows = []
on Windows, update far less often on filesystem changes. (#3601) By increasing the window size for collecting filesystem events, knowing that each event is processed in parallel, we might be lucky and that already reduces the likelyhood of clashes. It's an experiment though. On Unix, run with: `LOG_LEVEL=debug pnpm tauri dev --features adapt-to-windows`
2024-04-25 08:16:41 +03:00
add `watcher` crate with code copied from `gitbutler-tauri/src/watcher`. It's not functional yet, but exactly at the spot where it needs fixing across the boundary that is: - a stand-in for application events - analytics
2024-04-17 20:11:24 +03:00
[lib]
doctest = false
[dependencies]
The watcher-crate compiles and tests run
2024-04-17 21:56:14 +03:00
gitbutler-analytics.workspace = true
add `watcher` crate with code copied from `gitbutler-tauri/src/watcher`. It's not functional yet, but exactly at the spot where it needs fixing across the boundary that is: - a stand-in for application events - analytics
2024-04-17 20:11:24 +03:00
gitbutler-core.workspace = true
thiserror.workspace = true
anyhow = "1.0.81"
futures = "0.3.30"
optimize tokio features Previously, the attempt was made to enable only those `tokio` features that are actually used. However, due to default-features still being enabled and `tauri` using the `full` feature, for most intents and purposes that wasn't effective. Now default features are disabled, and `full` isn't used anymore, forcing all crates to mention the exact features they need. Note that `tracing` is missing here, as it wasn't effective previously without the `--cfg tokio_unstable` option also being specified as rustflag.
2024-04-18 10:25:40 +03:00
tokio = { workspace = true, features = [ "macros" ] }
add `watcher` crate with code copied from `gitbutler-tauri/src/watcher`. It's not functional yet, but exactly at the spot where it needs fixing across the boundary that is: - a stand-in for application events - analytics
2024-04-17 20:11:24 +03:00
tokio-util = "0.7.10"
tracing = "0.1.40"
backoff = "0.4.0"
notify = { version = "6.0.1" }
notify-debouncer-full = "0.3.1"
crossbeam-channel = "0.5.12"
itertools = "0.12"
[dev-dependencies]
gitbutler-testsupport.workspace = true
The watcher-crate compiles and tests run
2024-04-17 21:56:14 +03:00
git2.workspace = true
tempfile = "3.10"
once_cell = "1.19"
add `watcher` crate with code copied from `gitbutler-tauri/src/watcher`. It's not functional yet, but exactly at the spot where it needs fixing across the boundary that is: - a stand-in for application events - analytics
2024-04-17 20:11:24 +03:00
[lints.clippy]
all = "deny"
perf = "deny"
correctness = "deny"
Reference in New Issue Copy Permalink