# Try working around spurious rebuild bug in cargo \(\#41015\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/003a39740a29e888f63e9631a8d364dccaa88c92)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 003a39740a29e888f63e9631a8d364dccaa88c92

Requested commit: 003a39740a29e888f63e9631a8d364dccaa88c92

Commit: 003a39740a29e888f63e9631a8d364dccaa88c92

Tree: 494aa75f924f2b2fa4f76efa75a578afce28fd5e

Author: Lukas Wirth

Committer: GitHub

## Message

```
Try working around spurious rebuild bug in cargo (#41015)

We've been seeing a lot of weird constant rebuilds recently with
rust-anaylzer's check, either with cargo thinking build scripts are too
new timestamp wise or all fingerprints having gone missing somehow
(???). Reading through some related bug reports hints at disabling
incremental potentially working around this for now so let's test that
out

cc https://github.com/rust-lang/cargo/issues/16104

Release Notes:

- N/A *or* Added/Fixed/Improved ...
```

## Parents

- [33ec545d1fae5d65da11c0395470f76e9e8aaebd](https://git.cafe/gitcafe/zed/commit/33ec545d1fae5d65da11c0395470f76e9e8aaebd?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/003a39740a29e888f63e9631a8d364dccaa88c92?format=markdown)