Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

cant build

Open
#41 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
build-system

Research direction

Start by reproducing the failure with cargo build and inspect the vendored chrono source at F:\github\DesktopUI\vendor\chrono\src/offset/mod.rs. Compare the reported expected and actual checksums and determine whether the vendored source should remain unchanged; done means the project builds successfully or the required source change is clearly documented.

Written by the indexing model from the issue text.

Description

i use cargo build,but cant build success。
error: the listed checksum of F:\github\DesktopUI\vendor\chrono\src/offset/mod.rs has changed:
expected: a1036f75fc686603b216f9bb45b1689c8b34198b617b204800ceafb87b66ec45
actual: f40c95ba4c6759e378c35c44790c635472201f3d6feb86c1b8518e9f43537ddb

directory sources are not intended to be edited, if modifications are required then it is recommended that [patch] is used with a forked copy of the source

Dominant language
C
Stars
233
Forks
43
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from zerotier/DesktopUI

All issues in zerotier/DesktopUI

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.