Merge branch 'master' of ssh://git-annex.branchable.com
This commit is contained in:
commit
4eb6a2966a
8 changed files with 97 additions and 0 deletions
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joeyh.name/"
|
||||
ip="4.153.8.30"
|
||||
subject="comment 4"
|
||||
date="2012-09-09T16:53:35Z"
|
||||
content="""
|
||||
Perhaps the solution is to make --fast the default and to make it copy files when the content in the annex already has a hard link to it.
|
||||
"""]]
|
|
@ -0,0 +1,12 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joeyh.name/"
|
||||
ip="4.153.8.30"
|
||||
subject="comment 1"
|
||||
date="2012-09-09T16:45:20Z"
|
||||
content="""
|
||||
This is very strange behavior for gpg, it's being told several ways not to be interactive (--batch, --no-tty, --passphrase-fd); the mode it's being run in should, even without those options, only prompt for a password.
|
||||
|
||||
I'm left wondering what settings you have in gpg.conf, and even wondering if you have some kind of wrapper around gpg that makes it more interactive, or some odd gpg agent that's interactive, or something.
|
||||
|
||||
(I'm also confused that you mention a \"gpg>\" prompt, but your transcript doesn't show one.)
|
||||
"""]]
|
|
@ -0,0 +1,12 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joeyh.name/"
|
||||
ip="4.153.8.30"
|
||||
subject="comment 2"
|
||||
date="2012-09-09T16:50:40Z"
|
||||
content="""
|
||||
Perhaps you mistook the \"(gpg)\" that git-annex prints out for a gpg prompt? If your transcript is accurate, things seem to be stalled, and gpg is not behaving like you're at a prompt when you type stuff to it, just the terminal is echoing back what you typed.
|
||||
|
||||
This then looks like it might be the same bug someone else mentioned here <http://git-annex.branchable.com/design/assistant/blog/day_70__adding_ssh_remotes/#comment-048f7fad45dc545f9d5a560491b275a1>
|
||||
|
||||
I have not managed to reproduce that problem. Are you seeing stalls with any particular size of file? Does it happen with very small files?
|
||||
"""]]
|
|
@ -0,0 +1,8 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joeyh.name/"
|
||||
ip="4.153.8.30"
|
||||
subject="comment 3"
|
||||
date="2012-09-09T16:55:02Z"
|
||||
content="""
|
||||
I've replicated a stall with current git-annex head and gpg. Doesn't happen with an older build. bisecting..
|
||||
"""]]
|
|
@ -0,0 +1,13 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawmLB39PC89rfGaA8SwrsnB6tbumezj-aC0"
|
||||
nickname="Tobias"
|
||||
subject="comment 10"
|
||||
date="2012-09-09T16:58:55Z"
|
||||
content="""
|
||||
That's great news.
|
||||
|
||||
I suggest we disregard this comment thread, i'll just follow the proper bug report(which i guess i should have made to begin with).
|
||||
|
||||
Thanks for your good work.
|
||||
|
||||
"""]]
|
|
@ -0,0 +1,10 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joeyh.name/"
|
||||
ip="4.153.8.30"
|
||||
subject="comment 9"
|
||||
date="2012-09-09T16:52:33Z"
|
||||
content="""
|
||||
Someone else reported what looks like the same problem, here: [[bugs/transferkey_fails_due_to_gpg]]
|
||||
|
||||
I'mm be following up to that bug report. In fact, I think I just managed to replicate the bug!
|
||||
"""]]
|
|
@ -0,0 +1,24 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawmubB1Sj2rwFoVdZYvGV0ACaQUJQyiJXJI"
|
||||
nickname="Paul"
|
||||
subject="Hogging memory"
|
||||
date="2012-09-09T15:51:40Z"
|
||||
content="""
|
||||
How do you prefer bugs to be reported?
|
||||
|
||||
I'm having a problem where git-annex (from git, 1e41c0d85ecc24e8656bff79b2fba46c3663a054) is taking over 20GB of RAM after adding a single file.
|
||||
|
||||
To reproduce:
|
||||
|
||||
1. Create a new annex (I used the web app, created an annex at ~/annex)
|
||||
2. Add box.com as a remote, using encryption (followed <http://git-annex.branchable.com/tips/using_box.com_as_a_special_remote/>, basically `cd ~/annex; git annex initremote box.com type=directory directory=/media/box.com encryption=$GPGID`)
|
||||
3. copied a file into the annex (ok, I admit, the file was a bit large, 350MB, but still)
|
||||
4. refreshed the web app, nothing happened
|
||||
5. closed the web app
|
||||
6. started git annex assistant inside ~/annex
|
||||
7. git annex webapp
|
||||
8. noted that git annex noticed the file, and started transferring
|
||||
9. wait
|
||||
10. memory usage for the git-annex process goes beyond 21GB RAM
|
||||
11. oomkiller kills git-annex
|
||||
"""]]
|
|
@ -0,0 +1,10 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joeyh.name/"
|
||||
ip="4.153.8.30"
|
||||
subject="comment 2"
|
||||
date="2012-09-09T16:25:52Z"
|
||||
content="""
|
||||
The [[bugs]] page is the place to put bug reports like this so I won't forget them.
|
||||
|
||||
This should certianly not be happening. There are actually two git-annex processes running in the situation you describe; I'd be most curious to know whether the `git annex transfer` process was the one that blew up, or if the `git annex assistant` blew up. Also, it's not clear to me if you enabled the chunksize parameter when setting up the special remote, which could well be a significant detail.
|
||||
"""]]
|
Loading…
Add table
Reference in a new issue