Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | tested transferkeys restarting; fix some bugs | 2014-01-06 | |
| | |||
* | notes on long-running network connections | 2014-01-06 | |
| | |||
* | add back sha commands on OSX; SIGILL problem fixed | 2014-01-06 | |
| | |||
* | use strict version of map | 2014-01-06 | |
| | |||
* | assistant: Start a new git-annex transferkeys process after a network ↵ | 2014-01-06 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | connection change So that remotes that use a persistent network connection are restarted. A remote might keep open a long duration network connection, and could fail to deal well with losing the connection. This is particularly a concern now that we have external special reotes. An external special remote that is implemented naively might open the connection only when PREPARE is sent, and if it loses connection, throw errors on each request that is made. (Note that the ssh connection caching should not have this problem; if the long-duration ssh process loses connection, the named pipe is disconnected and the next ssh attempt will reconnect. Also, XMPP already deals with disconnection robustly in its own way.) There's no way for git-annex to know if a lost network connection actually affects a given remote, which might have a transfer in process. It does not make sense to force kill the transferkeys process every time the NetWatcher detects a change. (Especially because the NetWatcher sometimes polls 1 change per hour.) In any case, the NetWatcher only detects connection to a network, not disconnection. So if a transfer is in progress over the network, and the network goes down, that will need to time out on its own. An alternate approch that was considered is to use a separate transferkeys process for each remote, and detect when a request fails, and assume that means that process is in a failing state and restart it. The problem with that approach is that if a resource is not available and a remote fails every time, it degrades to starting a new transferkeys process for every file transfer, which is too expensive. Instead, this commit only handles the network reconnection case, and restarts transferkeys only once the network has reconnected and another transfer needs to be made. So, a transferkeys process will be reused for 1 hour, or until the next network connection. ---- The NotificationBroadcaster was rewritten to use TMVars rather than MSampleVars, to allow checking without blocking if a notification has been received. ---- This commit was sponsored by Tobias Brunner. | ||
* | format | 2014-01-06 | |
| | |||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2014-01-06 | |
|\ | |||
* | | close old tracking bug | 2014-01-06 | |
| | | |||
| * | (no commit message) | 2014-01-06 | |
| | | |||
* | | close | 2014-01-06 | |
| | | |||
* | | title | 2014-01-06 | |
| | | |||
* | | close | 2014-01-06 | |
| | | |||
* | | move wishlist item out out of bug list | 2014-01-06 | |
|/ | |||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2014-01-06 | |
|\ | |||
* | | close bug aboug defunct OSX Lion build | 2014-01-06 | |
| | | |||
| * | Added a comment: I'll start another thread | 2014-01-06 | |
| | | |||
| * | Added a comment | 2014-01-06 | |
| | | |||
| * | Added a comment | 2014-01-06 | |
| | | |||
| * | Added a comment | 2014-01-06 | |
| | | |||
| * | Added a comment | 2014-01-06 | |
| | | |||
| * | Added a comment | 2014-01-06 | |
| | | |||
* | | tag moreinfo since an example of such a repository is needed | 2014-01-06 | |
| | | |||
| * | Added a comment | 2014-01-06 | |
| | | |||
| * | Added a comment | 2014-01-06 | |
| | | |||
| * | Added a comment | 2014-01-06 | |
| | | |||
| * | Added a comment | 2014-01-06 | |
| | | |||
* | | no more OSX lion builds | 2014-01-06 | |
| | | |||
| * | typos | 2014-01-06 | |
| | | |||
| * | added link to Dropbox file naming limitations | 2014-01-06 | |
| | | |||
| * | (no commit message) | 2014-01-06 | |
| | | |||
| * | Added a comment | 2014-01-06 | |
| | | |||
| * | (no commit message) | 2014-01-06 | |
|/ | |||
* | devblog | 2014-01-05 | |
| | |||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2014-01-05 | |
|\ | |||
* \ | Merge branch 'master' of ssh://git-annex.branchable.com | 2014-01-05 | |
|\ \ | |||
| | * | Added a comment | 2014-01-06 | |
| |/ | |||
* | | assistant: Fixed several minor memory leaks that manifested when adding a ↵ | 2014-01-05 | |
| | | | | | | | | large number of files. | ||
| * | Added a comment: exactly this use case: cloud remotes too small | 2014-01-06 | |
| | | |||
* | | add notes on full profiling | 2014-01-05 | |
| | | |||
| * | Added a comment | 2014-01-05 | |
| | | |||
| * | Added a comment | 2014-01-05 | |
| | | |||
| * | Added a comment | 2014-01-05 | |
| | | |||
| * | Added a comment | 2014-01-05 | |
| | | |||
* | | add: Fix rollback when disk is completely full. | 2014-01-05 | |
|/ | | | | | | | | Noticed that it was possible for add to move a file to .git/annex/objects and not make the link if the disk was full. This happened because the location log update failed, and so addLink never got a chance to run. Running addLink first fixes it; on error it will unwind by moving the file back to where it was originally. | ||
* | fix form of quvi url | 2014-01-05 | |
| | |||
* | Merge branch 'master' of ssh://git-annex.branchable.com | 2014-01-05 | |
|\ | |||
* | | check if quvi page url has already been downloaded before | 2014-01-05 | |
| | | | | | | | | | | | | That is the url that is typically stored in the git-annex branch. Kept the check for the video url too, just in case. | ||
| * | (no commit message) | 2014-01-05 | |
| | | |||
| * | lost a bit of the error message, now complete | 2014-01-04 | |
| | | |||
| * | escape quote | 2014-01-04 | |
| | |