e213ef310f
* Fix minor FD leak in journal code. Closes: #754608 * direct: Fix handling of case where a work tree subdirectory cannot be written to due to permissions. * migrate: Avoid re-checksumming when migrating from hashE to hash backend. * uninit: Avoid failing final removal in some direct mode repositories due to file modes. * S3: Deal with AWS ACL configurations that do not allow creating or checking the location of a bucket, but only reading and writing content to it. * resolvemerge: New plumbing command that runs the automatic merge conflict resolver. * Deal with change in git 2.0 that made indirect mode merge conflict resolution leave behind old files. * sync: Fix git sync with local git remotes even when they don't have an annex.uuid set. (The assistant already did so.) * Set gcrypt-publish-participants when setting up a gcrypt repository, to avoid unncessary passphrase prompts. This is a security/usability tradeoff. To avoid exposing the gpg key ids who can decrypt the repository, users can unset gcrypt-publish-participants. * Install nautilus hooks even when ~/.local/share/nautilus/ does not yet exist, since it is not automatically created for Gnome 3 users. * Windows: Move .vbs files out of git\bin, to avoid that being in the PATH, which caused some weird breakage. (Thanks, divB) * Windows: Fix locking issue that prevented the webapp starting (since 5.20140707). # imported from the archive
17 lines
1 KiB
Markdown
17 lines
1 KiB
Markdown
Some neat stuff is coming up, but today was a pretty blah day for me.
|
|
I did get the Cronner tested and working (only had a few little bugs). But
|
|
I got stuck for quite a while making the Cronner stop `git-annex fsck`
|
|
processes it was running when their jobs get removed. I had some code to do
|
|
this that worked when run standalone, but not when run from git-annex.
|
|
|
|
After considerable head-scratching, I found out this was due to
|
|
`forkProcess` masking aync exceptions, which seems to be probably
|
|
[a bug](http://ghc.haskell.org/trac/ghc/ticket/8433). Luckily was able to
|
|
work around it. Async exceptions continue to strike me as the worst part of
|
|
the worst part of Haskell (the worst part being exceptions in general).
|
|
|
|
Was more productive after that.. Got the assistant to automatically queue
|
|
re-downloads of any files that fsck throws out due to having bad contents,
|
|
and made the webapp display an alert while fscking is running, which will
|
|
go to the page to configure fsck schedules. Now all I need to do is
|
|
build the UI of that page.
|