netwatch: chrono is built on Windows but never used
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 33/100
Research direction
In the Windows-specific netwatch dependency setup, remove the direct chrono version line and disable wmi's default features as described. Start by reading the netwatch Cargo.toml entries and check the existing draft pull request for the proposed two-line change. Done when the Windows-target cargo check passes and cargo tree --target all -i chrono shows no compiled dependency path.
Written by the indexing model from the issue text.
Description
On Windows, netwatch depends on wmi with default features, which pulls in chrono, plus a direct chrono = "0.4.23" line that only pins a minimum version. netwatch reads one string field from WMI (the default route's interface name) and never touches a date type. Seen on netwatch 0.20.2 and on main at 40fc258.
chrono is now flagged unmaintained (RUSTSEC-2026-0543), and you already ignore that in deny.toml. Dropping the direct line and using wmi with default-features = false stops it from being built. The change is two lines and waits here as a draft: https://github.com/irsync-dev/net-tools/pull/1
With it, cargo check -p netwatch --target x86_64-pc-windows-msvc --all-targets passes and cargo tree --target all -i chrono is empty. chrono stays in Cargo.lock as an optional dependency of wmi, but nothing compiles it.
#226 would make this moot by removing WMI altogether, but this is small and could land first. Happy to send the PR if you want it.
- Dominant language
- Rust
- Stars
- 34
- Forks
- 56
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 8
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from n0-computer/net-tools
-
netwatch: objc2-system-configuration with default features pulls objc2-security into every macOS buildPossibly taken @flub claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
n0-computer/net-tools#278 · 2 comments ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
n0-computer/net-tools#276 ·
Maintainers usually reply within 2 days
-
netwatch never turns on noq-udp's Apple fast path, so iroh's `fast-apple-datapath` does nothingOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
n0-computer/net-tools#272 ·
Maintainers usually reply within 2 days
-
Windows: endpoints hang or crash when several bind at once (concurrent WMI default-route queries?)Open
Difficulty 4/5 3-5 days Newbie friendliness 55/100
n0-computer/net-tools#271 ·
Maintainers usually reply within 2 days
-
portmapper: synchronous HomeRouter lookup blocks the Tokio workerPossibly taken @TNTcraftHIM claimed this 19 days ago. Openready-for-pr
Difficulty 3/5 1-2 days Newbie friendliness 50/100
n0-computer/net-tools#266 · 1 comment ·
Maintainers usually reply within 2 days
All issues in n0-computer/net-tools
Similar issues
-
area:web kind:bug priority:p2 ready
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 84/100
sims1253/r-typeshed#140 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
storytold/craft-libs#2867 ·
Maintainers usually reply within 1 day
-
help wanted needs investigation priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 62/100