diff options
13 files changed, 196 insertions, 2 deletions
diff --git a/doc/bugs/Cannot_sync_repos_setup_using_webapp:___34__git-annex-shell:_Only_allowed_to_access___126____47__foo_not___126____47__bar__47____34__/comment_2_807ef1250237bf4426e3a24c1f9ba357._comment b/doc/bugs/Cannot_sync_repos_setup_using_webapp:___34__git-annex-shell:_Only_allowed_to_access___126____47__foo_not___126____47__bar__47____34__/comment_2_807ef1250237bf4426e3a24c1f9ba357._comment new file mode 100644 index 000000000..625c12fbf --- /dev/null +++ b/doc/bugs/Cannot_sync_repos_setup_using_webapp:___34__git-annex-shell:_Only_allowed_to_access___126____47__foo_not___126____47__bar__47____34__/comment_2_807ef1250237bf4426e3a24c1f9ba357._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://launchpad.net/~maestro-alubia" + nickname="maestro-alubia" + subject="Thanks!" + date="2013-04-17T22:55:24Z" + content=""" +Thank you very much for the fast fix! I will try that soon. + +I love git-annex, keep up the excellent work :) +"""]] diff --git a/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_4_eaa7ffb3a1d9ffd6d89de301bd2cd5b2._comment b/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_4_eaa7ffb3a1d9ffd6d89de301bd2cd5b2._comment new file mode 100644 index 000000000..413ad8612 --- /dev/null +++ b/doc/bugs/Direct_mode_keeps_re-checksuming_duplicated_files/comment_4_eaa7ffb3a1d9ffd6d89de301bd2cd5b2._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawm5iosFbL2By7UFeViqkc6v-hoAtqILeDA" + nickname="Laszlo" + subject="comment 4" + date="2013-04-18T05:56:41Z" + content=""" +Ok, seems like it is fixed in latest (2013.04.17) release. + +Laszlo + +"""]] diff --git a/doc/bugs/Resource_exhausted.mdwn b/doc/bugs/Resource_exhausted.mdwn new file mode 100644 index 000000000..4c76c0901 --- /dev/null +++ b/doc/bugs/Resource_exhausted.mdwn @@ -0,0 +1,43 @@ +What steps will reproduce the problem? +My annex dir has 23459 files and uses 749MB disk space. +Just create a repository put this dir inside, and git-annex will crash. + +What is the expected output? What do you see instead? +I expect git-annex handles large number of files, and does not watch every single file of it. + +What version of git-annex are you using? On what operating system? +I'm using git-annex linux build, version 2013.04.17. + +Please provide any additional information below. + + [2013-04-17 23:52:35 CEST] Transferrer: Downloaded pappas_hu..di_44.jpg + git-annex: runInteractiveProcess: pipe: Too many open files + Committer crashed: lsof: createProcess: resource exhausted (Too many open files) + [2013-04-17 23:53:52 CEST] Committer: warning Committer crashed: lsof: createProcess: resource exhausted (Too many open files) + git-annex: runInteractiveProcess: pipe: Too many open files + git: createProcess: resource exhausted (Too many open files) + DaemonStatus crashed: /home/user/Desktop/down/annex_test/.git/annex/daemon.status.tmp21215: openFile: resource exhausted (Too many open files) + [2013-04-17 23:57:24 CEST] DaemonStatus: warning DaemonStatus crashed: /home/user/Desktop/down/annex_test/.git/annex/daemon.status.tmp21215: openFile: resource exhausted (Too many open files) + git-annex: runInteractiveProcess: pipe: Too many open files + git: createProcess: resource exhausted (Too many open files) + git-annex: runInteractiveProcess: pipe: Too many open files + NetWatcherFallback crashed: git: createProcess: resource exhausted (Too many open files) + [2013-04-18 00:27:17 CEST] NetWatcherFallback: warning NetWatcherFallback crashed: git: createProcess: resource exhausted (Too many open files) + git-annex: runInteractiveProcess: pipe: Too many open files + git-annex: git: createProcess: resource exhausted (Too many open files) + git-annex: accept: resource exhausted (Too many open files) + +Instead of raising system's limit (which is a neverending story), can we make git-annex only watch a directory and not every file of it? + +Or could the user specify some directory which he knows it is rarely change, to not be watched only check it once a day? + +The best would be if git annex could automatically adapt itself. +Ie. it watches eg. 200 files, and if some of it does not change for three days, then it drops from the watching basket, and those who changed (noticed while sanity checked) it adds to the basket. + +I don't really want to raise the ulimit, because my ultimate goal is to have git-annex on multiple raspberry pi with external harddrive (one at my home, one at my mom's home, one at my friends home, etc, etc). And raspberry is fairly low on resource. + +I'm interested in your thoughts. + +Best, + Laszlo + diff --git a/doc/bugs/Resource_exhausted/comment_1_a5ef7a62d4ed9365f9448520bb17e3b5._comment b/doc/bugs/Resource_exhausted/comment_1_a5ef7a62d4ed9365f9448520bb17e3b5._comment new file mode 100644 index 000000000..9bd4b0779 --- /dev/null +++ b/doc/bugs/Resource_exhausted/comment_1_a5ef7a62d4ed9365f9448520bb17e3b5._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawm5iosFbL2By7UFeViqkc6v-hoAtqILeDA" + nickname="Laszlo" + subject="comment 1" + date="2013-04-18T06:20:13Z" + content=""" +Once resource exhausted git-annex has git [defunct] process too. + +"""]] diff --git a/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_14_483244b1ed5744308022465f45c091fd._comment b/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_14_483244b1ed5744308022465f45c091fd._comment new file mode 100644 index 000000000..8594e5d75 --- /dev/null +++ b/doc/bugs/When_syncing_two_repositories__44___git_annex_uses_9x_times_diskspace/comment_14_483244b1ed5744308022465f45c091fd._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawm5iosFbL2By7UFeViqkc6v-hoAtqILeDA" + nickname="Laszlo" + subject="comment 14" + date="2013-04-18T05:54:09Z" + content=""" +Hi, these bugs (too detailed logging) and duplicated files issues are both solved in the latest (2013.04.17) release. + +Thank you very much, you can close this issue. + +Best, + Laszlo + +"""]] diff --git a/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_7_4ef107d70647780eb5347cae6f467fed._comment b/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_7_4ef107d70647780eb5347cae6f467fed._comment new file mode 100644 index 000000000..f7ca0a5af --- /dev/null +++ b/doc/bugs/git-annex_thinks_files_are_in_repositories_they_are_not/comment_7_4ef107d70647780eb5347cae6f467fed._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnSenxKyE_2Z6Wb-EBMO8FciyRywjx1ZiQ" + nickname="Walter" + subject="comment 7" + date="2013-04-17T20:50:34Z" + content=""" +So looking in .git/annex/objects, it is obvious that the difference between New1 and New1.txt is the extension. + +So, I think that explains all the things I was seeing. I guess the main point of confusion (though I can't think of a better way) is the distinction between data stored in .git/annex/objects, and files in the working folder. +If I thought in terms of hashes, that is all that would need to be shown in git annex whereis is which hashes are where (and then it would be obvious if several files have the same hash, that once one of them is present somewhere then all of them are). + +"""]] diff --git a/doc/bugs/git_annex_assistant_--autostart_failed.mdwn b/doc/bugs/git_annex_assistant_--autostart_failed.mdwn new file mode 100644 index 000000000..1657b70cc --- /dev/null +++ b/doc/bugs/git_annex_assistant_--autostart_failed.mdwn @@ -0,0 +1,38 @@ +**What steps will reproduce the problem?** + +Run *git annex assistant --autostart* + + git-annex autostart in /home/tobru/annex/repo1 + failed + git-annex autostart in /home/tobru/annex/repo2 + failed + git-annex autostart in /home/tobru/annex/repo3 + failed + git-annex autostart in /home/tobru/annex/repo4 + failed + git-annex autostart in /home/tobru/annex/repo5 + failed + +Running *git annex assistant* in each directory starts the assistant without errors. + +What could cause autostart to fail? Is there any log? Or a --debug parameter? + + +**What is the expected output? What do you see instead?** + +The assistant should start on all known repositories + +**What version of git-annex are you using? On what operating system?** + +4.20130417-g4bb97d5 on Ubuntu + +**Please provide any additional information below.** + +The ~/.config/git-annex/autostart file looks like this: + + /home/tobru/annex/repo1 + /home/tobru/annex/repo2 + /home/tobru/annex/repo3 + /home/tobru/annex/repo4 + /home/tobru/annex/repo5 + diff --git a/doc/design/assistant/blog/day_240__it_builds.mdwn b/doc/design/assistant/blog/day_240__it_builds.mdwn index 85e3dad6f..dc975af81 100644 --- a/doc/design/assistant/blog/day_240__it_builds.mdwn +++ b/doc/design/assistant/blog/day_240__it_builds.mdwn @@ -3,7 +3,7 @@ Late last night, I successfully built the full webapp for Android! That was with several manual modifications to the generated code, which I still need to automate. And I need to set up the autobuilder properly still. And I need to find a way to make the webapp open Android's web browser -to url. So it'll be a while yet until a package is available +to URL. So it'll be a while yet until a package is available to try. But what a milestone! The point I was stuck on all day yesterday was generated code that @@ -17,7 +17,7 @@ looked like this: That just couldn't type check at all. Most puzzling. My best guess is that `u_a2ehE` is the dictionary GHC passes internally to make a typeclass work, -which somehow here leaked out and became visible. Although +which somehow leaked out and became visible. Although I can't rule out that I may have messed something up in my build environment. The EvilSplicer has a hack in it that finds such code and converts it to something like this: diff --git a/doc/design/assistant/blog/day_240__it_builds/comment_1_151840ae0020ea63b2f041488c905386._comment b/doc/design/assistant/blog/day_240__it_builds/comment_1_151840ae0020ea63b2f041488c905386._comment new file mode 100644 index 000000000..a8e489582 --- /dev/null +++ b/doc/design/assistant/blog/day_240__it_builds/comment_1_151840ae0020ea63b2f041488c905386._comment @@ -0,0 +1,25 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawm5iosFbL2By7UFeViqkc6v-hoAtqILeDA" + nickname="Laszlo" + subject="Duplicated files resolved" + date="2013-04-18T05:52:35Z" + content=""" +Hi, + +Seems like the duplicated file issue finally resolved in this release, +also the logging is not so detailed, so it does not explode the disk space either. + +I think a new bug introduced in this release, +namely if you create a repository and a backup repository of it (pendrive), then this repository is not in direct mode by default. +(and there is a missing direct = True variable in that repository (/mnt/dat/annex_backup/.git/annex/config)). + +Also I run into resource exhausted bug, and every thread is crashed. +Can git-annex only watch a directory, and not every file in it? + +I will create a bugreport for resource exhausted. + +Best, + Laszlo + + +"""]] diff --git a/doc/install/OSX/comment_18_537fad5d8854e765499d47602d1ab398._comment b/doc/install/OSX/comment_18_537fad5d8854e765499d47602d1ab398._comment new file mode 100644 index 000000000..9d8d8f755 --- /dev/null +++ b/doc/install/OSX/comment_18_537fad5d8854e765499d47602d1ab398._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawkurjhi0CRJvgm7QNaZDWS9hitBtavqIpc" + nickname="Bret" + subject="Can't update" + date="2013-04-18T00:58:19Z" + content=""" +The laptop is one of the first macbook pro's with a 32 bit chip, which apple dropped support for in 10.7, so the furthest it can update to is 10.6.x. :( +"""]] diff --git a/doc/install/OSX/comment_19_18d4377f4ded5604d395d73783ba82c9._comment b/doc/install/OSX/comment_19_18d4377f4ded5604d395d73783ba82c9._comment new file mode 100644 index 000000000..f244951e8 --- /dev/null +++ b/doc/install/OSX/comment_19_18d4377f4ded5604d395d73783ba82c9._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://edheil.wordpress.com/" + ip="99.54.57.201" + subject="comment 19" + date="2013-04-18T02:05:34Z" + content=""" +sounds like a prime candidate for a nice lightweight linux distro ;) +"""]] diff --git a/doc/special_remotes/xmpp/comment_2_9fc3f512020b7eb2591d6b7b2e8de2d7._comment b/doc/special_remotes/xmpp/comment_2_9fc3f512020b7eb2591d6b7b2e8de2d7._comment new file mode 100644 index 000000000..02f70d0f2 --- /dev/null +++ b/doc/special_remotes/xmpp/comment_2_9fc3f512020b7eb2591d6b7b2e8de2d7._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmRFKwny4rArBaz-36xTcsJYqKIgdDaw5Q" + nickname="Andrew" + subject="comment 2" + date="2013-04-17T22:28:39Z" + content=""" +Yeah, I agree, this would be nice. + +For your own domain, you can configure DNS like this: [[http://support.google.com/a/bin/answer.py?hl=en&answer=34143]] to make XMPP find the right server. But for some that's not an option and the \"advanced\" mode would be useful in that case. +"""]] diff --git a/doc/todo/wishlist:_history_of_operations.mdwn b/doc/todo/wishlist:_history_of_operations.mdwn new file mode 100644 index 000000000..e5581a713 --- /dev/null +++ b/doc/todo/wishlist:_history_of_operations.mdwn @@ -0,0 +1,6 @@ +Hi, + +I would love to have a page of "history" or "events" in the webapp. Similar to how Dropbox or Box show it. +I've been using git-annex for my personal files for a few months now, and I feel like this is the only feature missing to start using it in a production multi-user environment. + +Thanks |