| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
which now have the necessary dependencies built.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
catching exceptions.
As seen in this bug report, the lifted exception handling using the StateT
monad throws away state changes when an action throws an exception.
http://git-annex.branchable.com/bugs/git_annex_fork_bombs_on_gpg_file/
.. Which can result in cached values being redundantly calculated, or other
possibly worse bugs when the annex state gets out of sync with reality.
This switches from a StateT AnnexState to a ReaderT (MVar AnnexState).
All changes to the state go via the MVar. So when an Annex action is
running inside an exception handler, and it makes some changes, they
immediately go into affect in the MVar. If it then throws an exception
(or even crashes its thread!), the state changes are still in effect.
The MonadCatchIO-transformers change is actually only incidental.
I could have kept on using lifted-base for the exception handling.
However, I'd have needed to write a new instance of MonadBaseControl
for the new monad.. and I didn't write the old instance.. I begged Bas
and he kindly sent it to me. Happily, MonadCatchIO-transformers is
able to derive a MonadCatchIO instance for my monad.
This is a deep level change. It passes the test suite! What could it break?
Well.. The most likely breakage would be to code that runs an Annex action
in an exception handler, and *wants* state changes to be thrown away.
Perhaps the state changes leaves the state inconsistent, or wrong. Since
there are relatively few places in git-annex that catch exceptions in the
Annex monad, and the AnnexState is generally just used to cache calculated
data, this is unlikely to be a problem.
Oh yeah, this change also makes Assistant.Types.ThreadedMonad a bit
redundant. It's now entirely possible to run concurrent Annex actions in
different threads, all sharing access to the same state! The ThreadedMonad
just adds some extra work on top of that, with its own MVar, and avoids
such actions possibly stepping on one-another's toes. I have not gotten
rid of it, but might try that later. Being able to run concurrent Annex
actions would simplify parts of the Assistant code.
|
| | |
|
| | |
|
| |
|
|
| |
build.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
rather buggy.
|
| |
|
|
| |
Based on a patch from Peter Simons
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Been meaning to do this for some time; Android port was last straw.
Note that newer versions of the uuid library have a Data.UUID.V4 that
generates random UUIDs slightly more cleanly, but Debian has an old version
of the library, so I do it slightly round-about.
|
| | |
|
| |
|
|
|
| |
wget is used due to having better progress output, but curl is used
in some cases where wget is not appropriate.
|
| |
|
|
| |
is available.
|
| | |
|
| | |
|
| |
|
|
| |
livedrive.com. Needs DAV version 0.3.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Old versions have an insufficiently generic definition of reader,
which only works on ReaderT and not on newtypes made of it, or something
like that.
|
| | |
|
| | |
|
| |
|
|
|
| |
Doesn't actually store anything yet, but initremote works and tests the
server.
|
| |
|
|
| |
Not needed.. At least for now..
|
| |
|
|
|
| |
My upload of -2 seems to have gotten lost, but there is a +b1 binNMU
that rebuilds against the new gnutls.
|
| |
|
|
|
|
| |
This adds a dep on haskell's async library, but since that's been
added to the recent haskell platform release, it should not be
much hardship to my poor long-suffering library chasing users.
|
| |
|
|
| |
debian testing still has the buggy version..
|
| |
|
|
|
| |
New 0.5 changes the api, rather gratuitously, so run away. I can juse use
Hamlet here.
|
| | |
|
| |
|
|
| |
which blaze-html depends on, so not a significant new dep
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Adjust build deps to ensure that only a fixed version of the library will
be used.
Also, removed the bound thread stuff, which I now think was (probably)
a red herring.
|
| | | |
|
| | |\
| |/
|/|
| |
| | |
Conflicts:
Assistant/Threads/NetWatcher.hs
|
| | |
| |
| |
| |
| |
| |
| |
| | |
MountWatcher can't do this, because it uses the session dbus,
and won't have access to the new DBUS_SESSION_BUS_ADDRESS if a new session
is started.
Bumped dbus library version, FD leak in it is fixed.
|
| | |\
| |/
|/| |
|
| | |
| |
| |
| |
| |
| |
| | |
For now, when dbus goes away, the assistant keeps running but does not fall
back or reconnect. To do so needs more changes to the DBus library; in
particular a connectSessionWith and connectSystemWith to let me specify
my own clientThreadRunner.
|
| |/ |
|
| |
|
|
| |
exception-safe versions of SampleVar and QSemN. Thanks, Ben Gamari for an excellent patch set.
|
| |
|
|
| |
webapp.
|
| |
|
|
| |
template haskell and thus yesod. (Should be available for arm soonish I hope).
|
| |
|
|
|
|
|
| |
At recommends it causes avahi-daemon to be pulled in on upgrade, which is
just too annoying to deal with avoiding on servers. MDNS is needed for
robust peering, but probably most desktop systems have it anyway; it's in
task-desktop.
|
Joey Hess