summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Avoid unncessary write to the location log when a file is unlocked and then ↵Gravatar Joey Hess2015-10-12
| | | | | | | | | | | | | | | added back with unchanged content. Implemented with no additional overhead of compares etc. This is safe to do for presence logs because of their locality of change; a given repo's presence logs are only ever changed in that repo, or in a repo that has just been actively changing the content of that repo. So, we don't need to worry about a split-brain situation where there'd be disagreement about the location of a key in a repo. And so, it's ok to not update the timestamp when that's the only change that would be made due to logging presence info.
* commentGravatar Joey Hess2015-10-12
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2015-10-12
|\
* | responseGravatar Joey Hess2015-10-12
| |
* | responseGravatar Joey Hess2015-10-12
| |
* | responseGravatar Joey Hess2015-10-12
| |
* | closeGravatar Joey Hess2015-10-12
| |
* | avoid ugly error about MVar if the sqlite worker thread crashesGravatar Joey Hess2015-10-12
| |
| * (no commit message)Gravatar efraim@78c5af2ab57cf0d7aa23bae3dd0adb700c98217c2015-10-11
| |
| * (no commit message)Gravatar tribut2015-10-11
| |
* | use action, not sideActionGravatar Joey Hess2015-10-11
| | | | | | | | | | | | | | | | sideAction is for things not generally related to the current action being performed. And, it adds a newline after the side action. This was not the right thing to use for stuff like "checksum", where doing a checksum is part of the git annex get process, and indeed we want it to display "(checksum...) ok"
| * Added a commentGravatar ovidiu@66ace8a8d99ce938b0538ffa0f26d30db02a96262015-10-11
| |
| * Added a commentGravatar dah2015-10-10
| |
| * Added a commentGravatar https://www.google.com/accounts/o8/id?id=AItOawnmF_9CAtfqdZkC4e-_dCX-rK5bqh4RWkw2015-10-10
| |
| * Added a commentGravatar ovidiu@66ace8a8d99ce938b0538ffa0f26d30db02a96262015-10-10
|/
* fix close tagGravatar Joey Hess2015-10-09
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2015-10-09
|\
* \ Merge branch 'dropproof'Gravatar Joey Hess2015-10-09
|\ \
* | | massive devblogGravatar Joey Hess2015-10-09
| | |
| * | add inAnnex check to local lockKeyGravatar Joey Hess2015-10-09
| | |
| * | close bugGravatar Joey Hess2015-10-09
| | |
| * | improve display when lockcontent failsGravatar Joey Hess2015-10-09
| | | | | | | | | | | | | | | | | | | | | | | | /dev/null stderr; ssh is still able to display a password prompt despite this Show some messages so the user knows it's locking a remote, and knows if that locking failed.
| * | implement lockContent for ssh remotesGravatar Joey Hess2015-10-09
| | |
| * | cleanup changelogGravatar Joey Hess2015-10-09
| | |
| * | also generate a drop safety proof for move --from remoteGravatar Joey Hess2015-10-09
| | |
| * | tests and verified that the bug is fixed, in all the cases I identifiedGravatar Joey Hess2015-10-09
| | |
| * | fix local dropping to not require extra locking of copies, but only that the ↵Gravatar Joey Hess2015-10-09
| | | | | | | | | | | | local copy be locked for removal
| * | improve message when drop failed due to no locked copyGravatar Joey Hess2015-10-09
| | |
| * | rename constructorGravatar Joey Hess2015-10-09
| | |
| * | verify local copy of content with lockingGravatar Joey Hess2015-10-09
| | |
| | * (no commit message)Gravatar wsha.code+ga@b38779424f41c5701bbe5937340be43ff1474b2d2015-10-09
| | |
| * | display drop safety proofs in debug modeGravatar Joey Hess2015-10-09
| | |
| | * Added a comment: post-receive hookGravatar wsha.code+ga@b38779424f41c5701bbe5937340be43ff1474b2d2015-10-09
| | |
| * | fix lockKey to run callback in original Annex monad, not local remote'sGravatar Joey Hess2015-10-09
| | |
| * | content locking during drop working for local git remotesGravatar Joey Hess2015-10-09
| | | | | | | | | | | | Only ssh remotes lack locking now
| * | finish and use lockContent interfaceGravatar Joey Hess2015-10-09
| | |
| * | improve drop proof codeGravatar Joey Hess2015-10-09
| | |
| * | refactorGravatar Joey Hess2015-10-09
| | |
| | * removedGravatar https://www.google.com/accounts/o8/id?id=AItOawnmF_9CAtfqdZkC4e-_dCX-rK5bqh4RWkw2015-10-09
| | |
| | * Added a commentGravatar https://www.google.com/accounts/o8/id?id=AItOawnmF_9CAtfqdZkC4e-_dCX-rK5bqh4RWkw2015-10-09
| | |
| | * Added a commentGravatar https://www.google.com/accounts/o8/id?id=AItOawnmF_9CAtfqdZkC4e-_dCX-rK5bqh4RWkw2015-10-09
| | |
| | * (no commit message)Gravatar https://www.google.com/accounts/o8/id?id=AItOawnmF_9CAtfqdZkC4e-_dCX-rK5bqh4RWkw2015-10-09
| | |
| | * Added a commentGravatar darkfeline2015-10-09
| | |
| | * (no commit message)Gravatar darkfeline2015-10-09
| | |
| | * Added a comment: Sharing S3 bucket between reposGravatar darkfeline2015-10-09
| | |
| * | TrustedCopy is good enough to allow droppingGravatar Joey Hess2015-10-08
| | | | | | | | | | | | | | | | | | | | | By definition, a trusted repository is trusted to always have its location tracking log accurate. Thus, it should never be in a position where content is being dropped from it concurrently, as that would result in the location tracking log not being accurate.
| * | try harder to verify until at least one VerifiedCopyLock is obtainedGravatar Joey Hess2015-10-08
| | | | | | | | | | | | | | | | | | | | | | | | | | | This avoids a failure where eg, we start with RecentlyVerifiedCopies for all remotes, and so didn't do any active verification, which is required. Also, dedup the list of VerifiedCopies when checking if we have enough, in case 2 copies of a UUID slip in.
| * | require 1 locked copy while dropping from local or a remoteGravatar Joey Hess2015-10-08
| | | | | | | | | | | | | | | | | | | | | | | | | | | See doc/bugs/concurrent_drop--from_presence_checking_failures.mdwn for discussion about why 1 locked copy is all we can require, and how this fixes concurrent dropping bugs. Note that, since nothing yet generates a VerifiedCopyLock yet, this commit breaks dropping temporarily.
| * | support invalidating existing VerifiedCopysGravatar Joey Hess2015-10-08
| | |
| * | add VerifiedCopy data typeGravatar Joey Hess2015-10-08
| | | | | | | | | | | | | | | | | | | | | | | | | | | There should be no behavior changes in this commit, it just adds a more expressive data type and adjusts code that had been passing around a [UUID] or sometimes a Maybe Remote to instead use [VerifiedCopy]. Although, since some functions were taking two different [UUID] lists, there's some potential for me to have gotten it horribly wrong.
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-09 19:49:36 +0000