| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
| |
network-3.0 changed some APIs in incompatible ways. Require an older
network for now.
|
| |
|
|
|
| |
hinotify-0.4 changed some types in incompatible ways. Require older
hinotify for now.
|
| |
|
|
| |
Turns out the mountpoints package is always required.
|
| |
|
|
|
| |
socks-0.6 changed an API in an incompatible way. Require an older socks
for now.
|
| | |
|
| |
|
|
|
| |
aws-0.20 changed some types in a backward-incompatible way. Update to
that package, and adjust calls accordingly.
|
| |
|
|
|
| |
Recent persistent requires more language extensions to generate
entities. Turn them on where appropriate.
|
| |
|
|
|
| |
base-4.11 made Semigroup a superclass of Monoid. Provide Semigroup
implementations for Monoids.
|
| |
|
|
|
|
|
|
|
|
| |
base-4.9 split MonadFail from Monad. Strengthen some type signatures to
require MonadFail instead of just Monad, derive MonadFail in relevant
places, and change a partial pattern match inside STM to one that
explicitly calls error. (STM is not a MonadFail; the user must
explicitly specify the desired semantics if a pattern match doesn’t work
out. In this case, the failing branch of the pattern should never be
reached, so crashing is fine.)
|
| |
|
|
|
| |
containers-0.6 removed insertWith' in favor of the Data.Map.Strict API.
Switch to the new API where appropriate.
|
| | |
|
| |
|
|
|
| |
This repository doesn’t contain the webapp. Remove dangling references
to it.
|
| |
|
|
| |
Supporting only one build system is simpler for now.
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Not yet used for everything else, but this is enough to
verify that it works, and do some benchmarking.
Some bugfixes included, which got it working. Also fallback to old
actions has been verified to work correctly.
Benchmarked dropping one thousand files from a ssh remote on localhost.
Using the old git-annex 40.867 seconds.
With the P2P protocol 9.905 seconds!
This commit was sponsored by Jochen Bartl on Patreon.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Make a Remote.Helper.P2P using code that was in Remote.P2P, converted to
use generic protocol runner actions.
This will allow it to be reused in Remote.Git.
This commit was sponsored by mo on Patreon.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Much like Remote.P2P, there's a pool of connections to a peer, in order
to support concurrent operations.
Deals with old git-annex-ssh on the remote that does not support p2pstdio,
by only trying once to use it, and remembering if it's not supported.
Made p2pstdio send an AUTH_SUCCESS with its uuid, which serves the dual
purposes of something to detect to see that the connection is working,
and a way to verify that it's connected to the right uuid.
(There's a redundant uuid check since the uuid field is sent
by git_annex_shell, but I anticipate that being removed later when
the legacy git-annex-shell stuff gets removed.)
Not entirely happy with Remote.Git.runSsh's behavior
when the proto action fails. Running the fallback will work ok, but what
will we do when the fallbacks later get removed? It might be better to
try to reconnect, in case the connection got closed.
This commit was sponsored by Boyd Stephen Smith Jr. on Patreon.
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Avoids ugly messages when forced ssh command is not git-annex-shell.
This commit was sponsored by Ole-Morten Duesund on Patreon.
|
| |\ |
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Not yet used by git-annex, but this will allow faster transfers etc than
using individual ssh connections and rsync.
Not called git-annex-shell p2p, because git-annex p2p does something
else and I don't want two subcommands with the same name between the two
for sanity reasons.
This commit was sponsored by Øyvind Andersen Holm.
|
| | |
| |
| |
| | |
This commit was sponsored by Fernando Jimenez on Patreon.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
lockContentShared had a screwy caveat that it didn't verify that the content
was present when locking it, but in the most common case, eg indirect mode,
it failed to lock when the content is not present.
That led to a few callers forgetting to check inAnnex when using it,
but the potential data loss was unlikely to be noticed because it only
affected direct mode I think.
Fix data loss bug when the local repository uses direct mode, and a
locally modified file is dropped from a remote repsitory. The bug
caused the modified file to be counted as a copy of the original file.
(This is not a severe bug because in such a situation, dropping
from the remote and then modifying the file is allowed and has the same
end result.)
And, in content locking over tor, when the remote repository is
in direct mode, it neglected to check that the content was actually
present when locking it. This could cause git annex drop to remove
the only copy of a file when it thought the tor remote had a copy.
So, make lockContentShared do its own inAnnex check. This could perhaps
be optimised for direct mode, to avoid the check then, since locking
the content necessarily verifies it exists there, but I have not bothered
with that.
This commit was sponsored by Jeff Goeke-Smith on Patreon.
|
| | |
| |
| |
| |
| |
| | |
This will be used by git-annex-shell when configured to be readonly.
This commit was sponsored by Nick Daly on Patreon.
|
| | | |
|
| | | |
|
| |/ |
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
| |
This commit was supported by the NSF-funded DataLad project.
|
| | |
|
| | |
|
| | |
|
Benjamin Barenblat
Joey Hess
hobbes@b2cacef69071743c3a831e60511062f7e014e52f
davicastro
andrew
https://tribut.de/
yarikoptic