fd0a147ae6
Request to terminate currently ongoing downloads and jump to the bumped file incoming in 3, 2, 1. Also, has a slightly strange effect where we pop a job off the queue, but the copyChannel is still busy and blocks, though it gets moved to the progress slice in the jobqueue, and looks like it's in progress which it isn't as it's waiting to be picked up from the copyChan. As a result, the progress emitter doesn't register on the task, and hence the file doesn't have a progress bar, but cannot be replaced by a bump. I guess I can fix progress bar issue by moving the progressEmiter.Register just before passing the file to the copyChan, but then we are back to the initial problem of a file with a progress bar, but no progress happening as it's stuck on write to copyChan I checked if there is a way to check for channel writeability (before popping) but got struck by lightning just for bringing the idea up in #go-nuts. My ideal scenario would be to check if copyChan is writeable, pop job from the queue and shove it down handleFile. This way jobs would stay in the queue while they cannot be handled, meaning that the `Bump` could bring your file up higher. |
||
|---|---|---|
| assets | ||
| cmd | ||
| docker | ||
| etc | ||
| Godeps | ||
| gui | ||
| internal | ||
| protocol | ||
| test | ||
| .gitignore | ||
| .mailmap | ||
| AUTHORS | ||
| build.go | ||
| build.sh | ||
| changelog.sh | ||
| check-contrib.sh | ||
| CONDUCT.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| NICKS | ||
| README.md | ||
syncthing
This is the syncthing project. The following are the project goals:
-
Define a protocol for synchronization of a folder between a number of collaborating devices. The protocol should be well defined, unambiguous, easily understood, free to use, efficient, secure and language neutral. This is the Block Exchange Protocol.
-
Provide the reference implementation to demonstrate the usability of said protocol. This is the
syncthingutility. It is the hope that alternative, compatible implementations of the protocol will come to exist.
The two are evolving together; the protocol is not to be considered stable until syncthing 1.0 is released, at which point it is locked down for incompatible changes.
Getting Started
Take a look at the getting started guide.
There are a few examples for keeping syncthing running in the background on your system in the etc directory.
There is an IRC channel, #syncthing on Freenode, for talking directly
to developers and users (when awake and present, etc.).
Building
Building Syncthing from source is easy, and there's a guide that describes it for both Unix and Windows.
Signed Releases
As of v0.7.0 and onwards, git tags and release binaries are GPG signed with the key BCE524C7 (http://nym.se/gpg.txt). For release binaries, MD5 and SHA1 checksums are calculated and signed, available in the md5sum.txt.asc and sha1sum.txt.asc files.
Documentation
The syncthing documentation is on the discourse site.
All code is licensed under the GPL, v3 or later.