mirror of
https://github.com/octoleo/syncthing.git
synced 2024-11-09 14:50:56 +00:00
b1b68ceedb
We have the invalid bit to indicate that a file isn't good. That's enough for remote devices. For ourselves, it would be good to know sometimes why the file isn't good - because it's an unsupported type, because it matches an ignore pattern, or because we detected the data is bad and we need to rescan it.
Or, and this is the main future reason for the PR, because it's a change detected on a receive only device. We will want something like the invalid flag for those changes, but marking them as invalid today means the scanner will rehash them. Hence something more fine grained is required.
This introduces a LocalFlags fields to the FileInfo where we can stash things that we care about locally. For example,
FlagLocalUnsupported = 1 << 0 // The kind is unsupported, e.g. symlinks on Windows
FlagLocalIgnored = 1 << 1 // Matches local ignore patterns
FlagLocalMustRescan = 1 << 2 // Doesn't match content on disk, must be rechecked fully
The LocalFlags fields isn't sent over the wire; instead the Invalid attribute is calculated based on the flags at index sending time. It's on the FileInfo anyway because that's what we serialize to database etc.
The actual Invalid flag should after this just be considered when building the global state and figuring out availability for remote devices. It is not used for local file index entries.
|
||
|---|---|---|
| .. | ||
| testdata | ||
| debug.go | ||
| deviceactivity_test.go | ||
| deviceactivity.go | ||
| devicedownloadstate_test.go | ||
| devicedownloadstate.go | ||
| doc.go | ||
| folder_sendonly.go | ||
| folder_sendrecv_test.go | ||
| folder_sendrecv.go | ||
| folder.go | ||
| folderstate.go | ||
| model_test.go | ||
| model.go | ||
| progressemitter_test.go | ||
| progressemitter.go | ||
| queue_test.go | ||
| queue.go | ||
| requests_test.go | ||
| sentdownloadstate.go | ||
| sharedpullerstate_test.go | ||
| sharedpullerstate.go | ||
| util.go | ||