mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

devblog

Browse source
This commit is contained in:
Joey Hess 2016-01-07 18:03:06 -04:00
parent 4b819bee2b
commit c96fb11a96
Failed to extract signature
2 changed files with 17 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
doc/devblog/day_354-355__beating_on_the_test_suite.mdwn Normal file
View file

@ -0,0 +1,8 @@
Been working hard on the last several test suite failures for v6 unlocked
files. Now I've solved almost all of them, which is a big improvement to
my confidence in its (almost) correctness.
Frustratingly, the test suite is still not green after all this work.
There's some kind of intermittent failure related to the sqlite database.
Only seems to happen when the test suite is running, and the error
message is simply "Error" which is making it hard to track down..

22
doc/todo/smudge.mdwn
View file

@ -5,19 +5,6 @@ git-annex should use smudge/clean filters.
* Intermittent sqlite related test suite failures, with: * Intermittent sqlite related test suite failures, with:
Exception: failed to commit changes to sqlite database: Just SQLite3 returned ErrorIO while attempting to perform step. Exception: failed to commit changes to sqlite database: Just SQLite3 returned ErrorIO while attempting to perform step.
sqlite worker thread crashed: SQLite3 returned ErrorError while attempting to perform step. sqlite worker thread crashed: SQLite3 returned ErrorError while attempting to perform step.
* Dropping a smudged file causes git status (and git annex status)
to show it as modified, because the timestamp has changed.
Getting a smudged file can also cause this.
Upgrading a direct mode repo also leaves files in this state.
User can use `git add` to clear it up, but better to avoid this,
by updating stat info in the index.
(May need to use libgit2 to do this efficiently, cannot find
any plumbing except git-update-index, which is very inneficient for
smudged files.)
** This causes some test suite failures; git merge fails when files
are in this state **
* Reconcile staged changes into the associated files database, whenever * Reconcile staged changes into the associated files database, whenever
the database is queried. This is needed to handle eg: the database is queried. This is needed to handle eg:
git add largefile git add largefile
@ -32,6 +19,15 @@ git-annex should use smudge/clean filters.
(And should avoid unlocking an object with a hard link if it's hard (And should avoid unlocking an object with a hard link if it's hard
linked to a shared clone, but that's already accomplished because it linked to a shared clone, but that's already accomplished because it
avoids unlocking an object if it's hard linked at all) avoids unlocking an object if it's hard linked at all)
* Dropping a smudged file causes git status (and git annex status)
to show it as modified, because the timestamp has changed.
Getting a smudged file can also cause this.
Upgrading a direct mode repo also leaves files in this state.
User can use `git add` to clear it up, but better to avoid this,
by updating stat info in the index.
(May need to use libgit2 to do this efficiently, cannot find
any plumbing except git-update-index, which is very inneficient for
smudged files.)
* Crippled filesystem should cause all files to be transparently unlocked. * Crippled filesystem should cause all files to be transparently unlocked.
Note that this presents problems when dealing with merge conflicts and Note that this presents problems when dealing with merge conflicts and
when pushing changes committed in such a repo. Ideally, should avoid when pushing changes committed in such a repo. Ideally, should avoid