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
989 B
Markdown
17 lines
989 B
Markdown
Lots of progress from yesterday's modest start of building data types for
|
|
scheduling. Last night I wrote the hairy calendar code to calculate when
|
|
next to run a scheduled event. (This is actually quite superior to `cron`,
|
|
which checks every second to see if it should run each event!) Today I
|
|
built a "Cronner" thread that handles spawning threads to handle each
|
|
scheduled event. It even notices when changes have been made to the its
|
|
schedule and stops/starts event threads appropriately.
|
|
|
|
Everything is hooked up, building, and there's a good chance it works
|
|
without too many bugs, but while I've tested all the pure code (mostly
|
|
automatically with quickcheck properties), I have not run the Cronner
|
|
thread at all. And there is some tricky stuff in there, like noticing
|
|
that the machine was asleep past when it expected to wake up, and deciding
|
|
if it should still run a scheduled event, or should wait until next time.
|
|
So tomorrow we'll see..
|
|
|
|
Today's work was sponsored by Ethan Aubin.
|